You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if I am missing something here or if I uncovered a memory leak. I was adding a Terminate event to TestSuite and noticed it doesn't fire.
PrivateSubClass_Terminate()Debug.Print"This should fire from TestSuite..."StopEndSub
I was trying to find out why this was being skipped over and I came across this rubberduck blog lazy-object-weak-reference.
By storing the TestCase objects in the Tests collection it seems like it stays in memory (possibly even all the TestCase objects as well then?). I don't know how to check if this actually is the case or if something else is going on preventing the event to fire.
I ran a test in which I set the collection to nothing and sure enough the Terminate event fires. Perhaps TestSuite should have it's own state of the various statuses of the tests vs holding references to all the TestCase classes?
The text was updated successfully, but these errors were encountered:
Not sure if I am missing something here or if I uncovered a memory leak. I was adding a
Terminate
event toTestSuite
and noticed it doesn't fire.I was trying to find out why this was being skipped over and I came across this rubberduck blog lazy-object-weak-reference.
By storing the
TestCase
objects in theTests
collection it seems like it stays in memory (possibly even all theTestCase
objects as well then?). I don't know how to check if this actually is the case or if something else is going on preventing the event to fire.I ran a test in which I set the collection to nothing and sure enough the
Terminate
event fires. PerhapsTestSuite
should have it's own state of the various statuses of the tests vs holding references to all theTestCase
classes?The text was updated successfully, but these errors were encountered: