Hello everyone,
I am currently faced with the task of implementing a Continuous Integration (CI) toolchain and the corresponding workflow for LabVIEW. A crucial component is the review process.
So after reaching a certain point in development - such as after a feature merge, milestone, or a set number of commit - an offline review is triggered. The reviewer then examines the code changes at a time that suits him and maybe schedule a ongoing peer review. There are several tools for text-based programming, like JetBrains Space, that efficiently support this review process. However, these tools are not really suitable for VIs due to their binary format. I've explored various options and come across some interesting approaches, but none of them seem to utilize a dedicated offline review tool / workflow for LabVIEW specifically.
https://forums.ni.com/t5/LabVIEW-Development-Best/Improving-Code-Quality-and-Performing-Code-Reviews
https://forums.ni.com/t5/North-Oakland-County-LabVIEW/Code-Review-and-VI-Analyzer-5-6-20
https://forums.ni.com/t5/Random-Ramblings-on-LabVIEW/SSDC-Document-Deep-Dive-Code-Review-Checklist
https://www.ni.com/en/shop/labview/doing-code-reviews.html
https://argentaconsult.com/_userfiles/pages/files/cla_2018_code_reviews.pdf
https://learn.ni.com/learning-paths/implementing-a-test-strategy-in-labview
Tom's LabVIEW Adventure : 4 - How to do Code Reviews
I would be interested to know whether any of you use such tools or workflows, perhaps with customizations, or whether you have developed your own solutions for the offline review process of VIs. What experiences have you had and which approaches or tools have made the review process easier for you? Or is the concept of an offline review unsuitable for LabVIEW in the first place?
I look forward to your suggestions and ideas!
