TestArchitect Corner: How to Use Jenkins in TestArchitect

Jenkins is a Continuous Integration (CI) tool that controls repeatable tasks in software development. Check out this guide to see how TestArchitect seamlessly integrates with Jenkins to establish a CI environment for Automated Testing.

With the rising popularity of Continuous Integration/Continuous Delivery (CI/CD), Continuous Testing (CT) is becoming a hot topic for discussion. Knowing that comprehensive tests are running smoothly is highly beneficial for the CI/CD pipeline; but, running tests can be both times- and resource-consuming—not to mention that tests can become boring and rigid! Using the repetitive characteristics of CI/CD and applying them to testing can be a way to address this.

A key component of Continuous Integration (CI) is the frequent running of automated tests to catch potential bugs as soon as they are introduced in the development process. The CI software life cycle involves a process of coding, building, testing, and bug-fixing, often at a rate of several iterations per day.

Most CI systems allow 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.

TestArchitect supports integration with all CI/CD tools––as long as the tools support command-line interfaces (CLI).

How to Integrate TestArchitect with Jenkins

Jenkins is a Java-based, open-source Continuous Integration (CI) tool that controls and monitors the execution of repeatable tasks in software development. TestArchitect incorporates features that allow it to be readily integrated into a Jenkins-based CI environment.

A typical Jenkins-based CI environment with integrated TestArchitect involves the following components:

  • Software development workstations with a common source control server such as SVN or CVS.
  • A Jenkins master server to manage the CI process.
  • One or more test execution machines. Each machine must be set up as both a TestArchitect controller and Jenkins slave.
  • At least one machine with TestArchitect installed to:
    • Allow for the development of tests in TestArchitect Client,
    • Provide a repository for test-related project items such as test modules and results, and
    • Generate execution batch files for the test controllers.

Note that TestArchitect may be installed on a Jenkins slave, but not on the Jenkins master.

Creating a Batch File

To establish a connection between TestArchitect and a Jenkins server, a batch file that includes executed test modules is required.

  1. Select a test module or test folder for execution, then click Execute on the toolbar.
  2. In the Execute Test dialog box, click the Advanced Settings tab.
  3. Select the Export result(s) to xUnit checkbox.
  4. Click to specify the path where the XML file is to be saved.


  5. In the Open dialog box, specify the path to the Jenkins slave workspace.
    • Note:
    • The Jenkins master machine is responsible for controlling and monitoring executed jobs on slave machines.
    • Jenkins slave machines are responsible for executing jobs.
  6. Click Open.
    • The specified installation path now appears in the Select a destination folder text box.
  7. Click Generate Batch File.
    • The Creation of a batch file complete message appears, letting you know that the batch file creation was successful.

Importing the Batch File

  1. On the Jenkins dashboard, select New Job.
  2. Enter a Job name and select a project category.
  3. Click OK.
    • The Config page appears.
  4. In the Build section, click the Add build step.
  5. In the drop-down list, select Execute Windows batch command.
  6. Enter the path to the batch file in the Command text box.
    • Note: The batch file must be stored on the Jenkins master machine. You must copy the generated batch files on the Jenkins slave machines and paste them into the Jenkins master machine.
  7. In the Post-Build Actions section, click Add post-build action.
  8. In the drop-down list, select Publish JUnit test result report.
  9. Enter *.xml into the Test report XMLs text box to specify that all XML files related to executing test modules are to be selected.
  10. Click Save.
TestArchitect Support Team
We are the TestArchitect Support team who will help you achieve Automation success. Creating a few dozen automated test cases is easy. Maintaining them overtime while scaling your test suite to thousands of tests is not. It needs the right mix of tools, methods, and expertise.

The Related Post

When configured with a Python harness, TestArchitect can be used to automate testing on software for custom hardware Unlike other proprietary and open source tools, that are able to automate only desktop, or mobile, TestArchitect (TA Test) has the ability to test the software that runs on hardware in the following ways: 1. TA can ...
Regardless of your current state of tools, building an effective Continuous Integration suite of significant automated regression tests is the key to moving to a higher level of confidence in today’s development world. In the evolution timeline of software development tools, new tools have recently proliferated. We have all been sold on collaboration, transparency and ...
Developers of large data-intensive software often notice an interesting — though not surprising — phenomenon: When usage of an application jumps dramatically, components that have operated for months without trouble suddenly develop previously undetected errors. For example, the application may have been installed on a different OS-hardware-DBMS-networking platform, or newly added customers may have account ...
The path to continuous delivery leads through automation Software testing and verification needs a careful and diligent process of impersonating an end user, trying various usages and input scenarios, comparing and asserting expected behaviours. Directly, the words “careful and diligent” invoke the idea of letting a computer program do the job. Automating certain programmable aspects ...
All too often, software development organizations look at automating software testing as a means of executing existing test cases faster. Very frequently there is no strategic or methodological underpinning to such an effort. The approach is one of running test cases faster is better, which will help to deliver software faster. Even in organizations that ...
The guide for CUI Automated Testing strategies, including chatbot testing and voice app testing. In the Software Testing industry, trends come and go that shape the future of testing. From Automation in Agile, to the DevOps era we are now in, trends are what evolve and improve our testing processes and ideologies. Currently, many researchers ...
When it comes to performance testing, be smart about what and how you automate Listen closely to the background hum of any agile shop, and you’ll likely hear this ongoing chant: Automate! Automate! Automate! While automation can be incredibly valuable to the agile process, there are some key things to keep in mind when it ...
For this interview, we talked to Greg Wester, Senior Member Technical Staff, Craig Jennings, Senior Director, Quality Engineering and Ritu Ganguly, QE Director at Salesforce. Salesforce.com is a cloud-based enterprise software company specializing in software as a service (SaaS). Best known for its Customer Relationship Management (CRM) product, it was ranked number 27 in Fortune’s 100 ...
One of my current responsibilities is to find ways to automate, as much as practical, the ‘testing’ of the user experience (UX) for complex web-based applications. In my view, full test automation of UX is impractical and probably unwise; however, we can use automation to find potential UX problems, or undesirable effects, even in rich, ...
Every once in a while a book is put together that should be read by every person with a relationship to software development. This book is one of them. Everyone dreams of automating their software testing, but few make it a reality. This down-to-earth book contains stories of 28 teams that went for it, including ...
Take 5 and test your knowledge on the Software Testing essentials covered in our March 2019 issue. Good luck!
There is no one recipe to make big testing a big success. It takes planning and careful execution of the various aspects, like test design, infrastructure and organization – a mix that can be different for each situation in which you may find yourself. In writing about big testing, the first question that comes up ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe