« first day (2693 days earlier)      last day (487 days later) » 

Duga
Duga
12:02 AM
REFRESH!
[Minesweeper] 72 Games Played. 46 Bombs Used. 10726 Moves Performed. 5 New Users
[Zomis/Duga] 2 commits
 
 
4 hours later…
Duga
Duga
3:39 AM
 
 
16 hours later…
Duga
Duga
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
> 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
 
 
3 hours later…
Duga
Duga
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.
 
Duga
Duga
11:47 PM
[rubberduck-vba/Rubberduck] 1436 stars vs. [decalage2/oletools] 1765 stars
 

« first day (2693 days earlier)      last day (487 days later) »