I had reason to run the NI DETT alongside VI tester this week to try and debug reference leaks in my code.
I found that VI Tester actually has leaks itself which may expain the performance slowdown as it increases the number of test that are run.
TestCase.lvclass:WaitOnTestComplete.vi has a consistent leak due the failure to close the VI reference that is opened...
TestSuite.lvclass:WaitOnTestComplete.vi appears to have the same leak.
GraphicalTestRunner.lvlib:Results Status Update Process__core.vi has a leak at some event registration function (I haven't looked at this one)
Thought I'd feed this back so that everyone gets this fixed.
;-)
Nice toolkit
I had reason to run the NI DETT alongside VI tester this week to try and debug reference leaks in my code. I found that VI Tester actually has leaks itself which may expain the performance slowdown as it increases the number of test that are run. TestCase.lvclass:WaitOnTestComplete.vi has a consistent leak due the failure to close the VI reference that is opened... TestSuite.lvclass:WaitOnTestComplete.vi appears to have the same leak. GraphicalTestRunner.lvlib:Results Status Update Process__core.vi has a leak at some event registration function (I haven't looked at this one)
Thought I'd feed this back so that everyone gets this fixed. ;-) Nice toolkit
Cheers James