12:02 AM
4 hours later…
16 hours later…
7:50 PM
> Hey all. I'm actually looking to exercise some VBA code using python's `pywin32` library and a legacy macro-enabled workbook.
Does any viable workaround exist to generating some _semblance_ of a coverage report on, for instance, a VBA module? I am a bit daunted by the prospect of having to debug hundreds and hundreds of lines containing legacy code to make sure my unit tests are covering all edge cases.
I understand that there are some fundamental issues as indicated by @retailcoder and
Does any viable workaround exist to generating some _semblance_ of a coverage report on, for instance, a VBA module? I am a bit daunted by the prospect of having to debug hundreds and hundreds of lines containing legacy code to make sure my unit tests are covering all edge cases.
I understand that there are some fundamental issues as indicated by @retailcoder and
> I'm actually looking to exercise some VBA code using python's `pywin32` library and a legacy macro-enabled workbook.
Does any viable workaround exist to generating some _semblance_ of a coverage report on, for instance, a VBA module? I am a bit daunted by the prospect of having to debug hundreds and hundreds of lines containing legacy code to make sure my unit tests are covering all edge cases.
I understand that there are some fundamental issues as indicated by @retailcoder and @MDoerner
Does any viable workaround exist to generating some _semblance_ of a coverage report on, for instance, a VBA module? I am a bit daunted by the prospect of having to debug hundreds and hundreds of lines containing legacy code to make sure my unit tests are covering all edge cases.
I understand that there are some fundamental issues as indicated by @retailcoder and @MDoerner
3 hours later…
10:52 PM
> @awa5114 stick
Debug.Print "{module}.{procedure}"
as the first line in every method, then see which modules and procedures are called. Compare to a list of all modules in the project to find the % hit. Use conditional compilation so these debug messages only appear in debug mode
> @awa5114 stick
Debug.Print "{module}.{procedure}"
as the first line in every method, then see which modules and procedures are called. Compare to a list of all modules in the project to find the % hit. Use conditional compilation so these debug messages only appear in debug mode.
> @awa5114 Very basic approach: stick
Debug.Print "{module}.{procedure}"
as the first line in every method, then see which modules and procedures are called. Compare to a list of all modules in the project to find the % hit. Use conditional compilation so these debug messages only appear in debug mode.
> @awa5114 Very basic approach: stick
Debug.Print "{module}.{procedure}"
as the first line in every method, then see which modules and procedures are called. Compare to a list of all modules in the project to find the % hit. Optionally use conditional compilation so these debug messages only appear in debug mode.
« first day (2693 days earlier) ← previous day next day → last day (487 days later) »
Transcript for
Oct19
Oct '2120
Oct21
VBA Rubberducking
This chat has moved to Discord: discord.gg/MYX9RECenJ