« first day (2621 days earlier)      last day (559 days later) » 

12:03 AM
REFRESH!
[Minesweeper] 77 Games Played. 49 Bombs Used. 11103 Moves Performed. 8 New Users
 
 
14 hours later…
1:59 PM
> Hey guys,
I waited a few days to see if anything else would add to this conversation but it seems to have run dry. I will go ahead and close this ticket as I seem to understand where you guys are approaching this project from.

Thanks for the awesome project, I use it everyday and was successfully able to set up a Test Driven Environment using this platform.

To share some knowledge, Ultimately the decision really is to separate production code from tests. This is one of the "accepted pr
 
 
2 hours later…
3:40 PM
 
 
1 hour later…
5:02 PM
> > This is one of the "accepted practices" in writing tests from all the research that I've made. [Rightly or wrongly]

That would be correct, but with VBA not having a "solution" level that "contains" multiple projects, it's much simpler to keep the tests in the same project; since there's never been a first-party unit testing framework for VBA, VBA-specific guidance is pretty much inexistent. If you browse through Rubberduck's source code, you see that indeed we do have all the tests in the
 
 
2 hours later…
7:21 PM
> Thanks for filling in the gaps in my knowledge for me. :)
 
7:51 PM
> The thing I like about having the tests in the VBA Project is that someone else picking up a project can look at the tests and see what the item under test is supposed to do and find edge cases or add new capability - knowing just where that new capability might best be implemented... IOW self-documenting code.
 
 
2 hours later…
9:47 PM
@jonadv personally I never use the Run button to run any code, I've always just launched a macro (or function) from the immediate pane.
Other than that, VBA can get "stuck" in that kind of running-but-not-quite state with a memory leak, i.e. some object is unreachable but still in memory.
 
10:27 PM
@jonadv not as runtime refcounts, no - but Rubberduck makes it trivial to find what's calling what from where, at design/compile time.
 
 
1 hour later…
11:48 PM
[rubberduck-vba/Rubberduck] 1391 stars vs. [decalage2/oletools] 1678 stars
 

« first day (2621 days earlier)      last day (559 days later) »