08-27-2017 09:14 AM - edited 09-02-2017 05:03 AM
At CSS we use the LabVIEW Unit Test Framework for unit testing. I have been creating some short introductory tutorial videos for our developers and customers, and have started sharing them on YouTube. There are three more videos to come which will cover user defined tests (which is where we write most of our tests), general guidelines that work for us, and an overview of add on tools we developed to complement the UTF.
LabVIEW Unit Testing: Part 1
LabVIEW Unit Testing: Part 2
If anyone is interested they can find the videos at https://www.youtube.com/channel/UCS8mp0OKZr0czagd4S7rh9A
08-28-2017 11:03 AM
Hi David,
Thanks for sharing your Unit Testing videos with this community. They are very cool!
I suggest you edit the post and embed your videos. Use the "camera" button on the toolbar and from there it is pretty self explanatory.
You can see how I have embedded the videos to this post:
Thanks again and welcome to the Unit Testing Group!
Fab
09-02-2017 05:05 AM
Thanks - I am glad you like them.
It has been a long time since I contributed on these forums and I didn't notice the embed video option. Thanks for pointing it out!
09-19-2017 08:35 AM
LabVIEW Unit Testing Part 3:
In this video we look at creating user defined tests using the LabVIEW UTF
09-19-2017 08:37 AM
LabVIEW Unit Testing Part 4:
I just wanted to clarify one of the recommendations in this video that I was recently questioned about. Where we say 'Don't attempt to write a test for every VI in the project' what we are really trying to get at is don't get to hung up about having 100% code coverage or a unit test for every single VI. For example if you write a VI that belongs to a library and you set it to be in private scope then this VI must be used by public VI in the library - therefore if you write a test for the public VI then the private VI will be indirectly tested.