2. Test and Record the Existing Behavior of Your VIs

LabVIEW 2018 Help

Edition Date: March 2018
Part Number: 371361R-01
View Product Info

DOWNLOAD (Windows Only)

LabVIEW 2016 Help
LabVIEW 2017 Help
LabVIEW 2018 Help
LabVIEW 2019 Help
LabVIEW 2020 Help

When you upgrade VIs, differences between the previous version of LabVIEW and LabVIEW 2018 can occasionally change the behavior of the VIs. If you test the VIs in both versions, you can compare the results to detect behavior changes specifically caused by upgrading. Therefore, verify that you have current results for any of the following tests:

  • Mass compile logs that identify the existence of broken VIs. Mass compiling your VIs before you upgrade is particularly useful if multiple people contribute to the development of the VIs or if you suspect that some of the VIs have not been compiled recently. To generate this mass compile log, place a checkmark in the Log Results checkbox of the Mass Compile dialog box.
  • Unit tests that verify whether individual VIs perform their intended functions correctly
  • Integration tests that verify whether a project or group of subVIs work together as expected
  • Deployment tests that verify whether VIs behave as expected when deployed to a target, such as a desktop or FPGA target
  • Performance tests that benchmark CPU usage, memory usage, and code execution speed. You can use the Profile Performance and Memory window to obtain estimates of the average execution speeds of the VIs.
  • Stress tests that verify whether the VIs handle unexpected data correctly
Note  If you changed any VIs as the result of testing, back up the new versions of the VIs before proceeding.
Previous: Back Up Your VIs and Machine Configuration Next: Install LabVIEW, Add-Ons, and Device Drivers


Not Helpful