Comments on: Unit Testing VI Properties

By: Jim Kring

Jim Kring — Thu, 19 Mar 2009 14:58:40 +0000

Alessandro: Please, let us know about your progress and if you have any questions about implementing a VI tester + One Click Build solution for your applications.

By: Alessandro Ricco

Alessandro Ricco — Thu, 19 Mar 2009 09:19:06 +0000

Omar and Jim VI tester + One Click Build could be a amazing. here i’m trying to use Agile methods and for sure Test Driven Development and Incremental Releases are what i consider the most valid methods, your tool can help to use this methods, definitivelly i’ll give it a try.

By: Jim Kring

Jim Kring — Wed, 18 Mar 2009 17:29:54 +0000

Alessandro: As Omar mentioned, you can run tests programmatically, now. If you incorporate this as a step in your One Click Build, then you can run your tests before building your EXE.

By: Omar Mussa

Omar Mussa — Wed, 18 Mar 2009 17:09:41 +0000

Alessandro – you can run tests automatically through the VI Tester programmatic API. VI Tester is an xUnit based test framework that is completely separate from NI’s test vector based UTF. You can find more about VI Tester by visiting: http://jkisoft.com/vi-tester

By: Omar Mussa

Omar Mussa — Wed, 18 Mar 2009 13:33:40 +0000

Another good use case for testing VI Properties is to validate that specific string data is present in the VI Description.

By: Alessandro Ricco

Alessandro Ricco — Wed, 18 Mar 2009 09:16:41 +0000

Very good example on how to use proficency your VI Tester. Another use case example could test VI for presence of breakpoints.
Just an ipotesis, can a set of test run automatically at deploy\compile time? This could be very usefull.
Another point is how JKI VI tester relates with NI LabVIEW Unit Test Framework Toolkit?

Ciao,
Alessandro