Jenkins is an open-source automation server that is commonly used to perform Continuous Integration (CI) tasks, such as the building, testing, and delivery of an application. You may choose to use TestStand in combination with Jenkins or other CI systems for one or more of the following use cases:
By continuously testing and building your code, CI practices can help identify problems early in the development process. For example - consider a team that shares test development between several engineers. If a subVI is not checked into the shared repository, the test sequence will run with no problems on the original development machine, but when the team runs code from the repository, this sequence will have a broken VI. A problem like this could be caught immediately by a CI server and corrected, saving the team from last-minute troubleshooting.
TestStand can also be used as part of a larger CI system. For example - consider a mixed team of software and hardware engineers that are developing an embedded device. Unit tests can be written to test the embedded software, and TestStand sequences can be written to test hardware requirements and the software/hardware integration. TestStand can publish test results back to the same CI server as the software unit tests, allowing the entire team to adopt test-driven development and work together to resolve any failing tests.