Share this post

Link to post

Share on other sites

This is a good idea, we'll look into it further. I think the reason that we shipped the testExample as a .vi instead of .vit is so that users could actually 'execute' the testCase that we create without any modifications to validate that their testCase *works*. Its partly because we weren't sure how much LVOOP experience our users would have so we wanted to minimize the effort for getting started, and that meant making it easy for users to see their testCase on the VI Tester GUI.

The runtime error you are seeing is because the way that we find tests to show on the VI Tester UI is via 'introspection' and it just happens that we're searching for VIs named test*.vi and test*.vit is being found as a 'match'. I've filed a bug for this (Case 7883) and added it to the known issues.

Share this post

Link to post

Share on other sites

The runtime error you are seeing is because the way that we find tests to show on the VI Tester UI is via 'introspection' and it just happens that we're searching for VIs named test*.vi and test*.vit is being found as a 'match'.

FWIW the error doesn't seem to hurt anything. I suppose I could just go into <Labview>\resource\JKI\VI Tester\Templates\TestCase and rename textExample.vi to Example.vit. Then I wouldn't have to rename it at all for new test cases.