Continuous Integration / Continuous Development - LabVIEW or TestStand?

[Austin Equitz]

My team currently uses LabVIEW to execute test cases on our products to verify requirements. These test cases are executed on a HIL (Hardware-in-the-Loop) test station.

Part of what we want to do is execute test cases in an automated fashion utilizing CI/CD. Here is an example of what this would look like:

1. A product firmware revision is committed to Bitbucket. Before the build server approves the build, it must be tested on the HIL.
2. The build server interacts with a requirements/test management tool that contains all of the necessary information about what test cases need to be executed.
3. The requirements/test management tool sends a request to the HIL to execute test cases.
4. The HIL receives that request and executes the test cases.
5. The test data (test artifacts such as reports and raw data) is sent back to the requirements/test management tool.
6. If the test cases passed successfully, the build is approved on the build server and can be officially used on our products.

 

My question is:

 

What is the better method for doing this? LabVIEW or TestStand?

Whatever method is chosen must be capable of receiving requests from the test management tool or being driven by the test management tool.

 

Below is a flow chart of how this process would look.