Jenkins is a Java-based open-source continuous integration (CI) tool that controls and
monitors the execution of repeatable tasks in software development. A key component of continuous
integration is the frequent running of automated tests to catch potential bugs as soon as they are
introduced in the development process. TestArchitect
incorporates features that allow it to be readily integrated into a Jenkins-based CI
- Ensure that the xUnit plugin is installed on the Jenkins server. The plug-in
provides useful information about test results, such as the historical trends. It offers a Web
interface for viewing test reports, tracking failures, and more.
- To avoid Java-related conflicts, do not install TestArchitect on the same host as your Jenkins master server.
The continuous integration software life cycle
involves a process of coding, building, testing, and bug-fixing, often at a rate of several
iterations per day.
The Jenkins CI system allows for much of this
cyclic process to be automated. Code commits can be set to trigger software builds; build
completion can trigger automated testing; and test results can be rapidly compiled, processed and
reported to allow bugs to be addressed in the coding process.
The Jenkins–TestArchitect environment
A typical Jenkins-based CI
environment with integrated TestArchitect
- Software development workstations with a common source control server such as SVN or
- A Jenkins master server, to manage the CI process
- One or more test execution machines. Each must be set up as both a TestArchitect controller
and Jenkins slave.
- At least one machine with TestArchitect
- allow for the development of tests in TestArchitect Client
- provide a repository for test-related project items such as test modules and results,
- generate execution batch files for the test controllers.
be installed on a Jenkins slave, but not on the Jenkins master.