Unit Test Framework and VIT's

[JÞB]

OK This is getting annoying. 

Open any project containing a vit.

Create a UT that uses the VIT as the vi under test.

Run the unit tests from the project.

Why oh Why are all those vi's from template in memory???? someone forgot to clean up?

[PeanutButterOven]

Hello Jeff,

I wanted to clarify the issue a little bit more. It sounds like you are testing a vi template and each test run creates a new copy of the VI in memory when it should be disposing of the VI between runs......is this a correct restatement of the issue you are encountering?

Mark B

[JÞB]

A little more complex.

Using LabVIEW 2011SP1 x32 on Win7-64. 

A project with UTs

the unit test launches a vi calling a VIT.  New VIT is created and placed in memory.

Unit test completes and passes (well, if you ignore the error source strings that get mutillated with {HHHHHHHHHHHHHHHHH})

return to the source project and look at items in memory............yup a bunch of Tested..vi##' s launched and were not removed from memory

Close all this project- Do not save all the viclones

Run a vi with an all vi's in memory p-node read (several hundred vi's in memory!!!! most from UTF!)

Close Project- (I can save or defer- I wanted to close no saving)

Now I've closed everything and Im back to the start screen...open new blank vi..... look at the lower left boarder WHAT!!!! i'm in the App instance of the closed project!!!!

Its a mess

[PeanutButterOven]

Jeff,

I will try look through the known issues for a work around, if I can't ind any I will try to reproduce the issue on my end.

[PeanutButterOven]

Jeff there are no known issues with the UTF that resemble the issue you described. Furthermore I was unable to reproduce the issue using LV 2011 SP1 with UTF.