Daklu
-
Posts
36 -
Joined
-
Last visited
-
Days Won
3
Posts posted by Daklu
-
-
Thanks Jim. It's not urgent, but I wanted to let you know about it.
Once I figured out it was related to classes being created in a previous version of VI Tester it was easy enough to work around.
-
I ran across a problem in a project where, after creating and initializing the class under test in the setUp VI, unbundling it in the test VI returns a default object rather than the one I instantiated.
setUp.vi
testCount.vi
I've attached a project with the class under test (ListImp) and two test cases. Both test cases have (as near as I can tell) identical setUp code and identical code in the test method (testCount). However, one test passes while the other test fails. Any idea what's causing this?
[Edit - The about box reports "version 3.0.1.294 (Feb 11 2019)".]
[Edit 2 - Another piece of potentially relevant information is the Test_ListImp..._2 test class was brought forward from an older version of VI Tester. I don't know what version, but according to my repository it was sometime before Feb. 2013. The other test class (the one that passed) was created with the current version of VI Tester.]
-
1
-
Strange VI Tester Failure (Object not carried from setUp to test method)
in VI Tester
Posted · Edited by Daklu
BTW, (and not related to this thread in any way whatsoever...) I cloned the repo to see if I could implement the changes for Issue #40 .
Package 3.0.2 is available on VIPM. Should that branch be merged into master or do you have other plans? (I'm wondering if I should branch from master or 95c579a.)