Automate testing as part of the continuous delivery/integration cycles

As testing becomes increasilingly embedded into the development and DevOp activities, it is extremely important to make test automation part to the continuous integration or delivery process. By doing this, testers can ensure that their tests are always targeting the latest version of the software and defects are caught as early as possible. This is easily achievable by using a tool like Jenkins to trigger the automated REST or UI tests every time developers commit code and the application under tests is deployed in the CI or Staging environment.  However, one of the challenges of following this process is the time that it takes to analyze test failures and keep track of known issues. Looking at the test reports generated by the framework (JUnit, TestNG, Cucumber, etc.) might be ok at first, but as the number of tests and the number of daily commits grows, this process may become overwhelming. TestRecon solves this problem by allowing the testing and development team view all test results in a central location and quickly identify trends like tests failing with the same error code or flaky tests. In addition, it allows users to link test failures to bugs, add notes to tests and even link back to screenshots or other artifacts, due to its web-based nature.

Contact us to for a free trial

Loading Test Results from Jenkins using the APIs

Loading test results from Jenkins to TestRecon is very simple. You set it up once and your test results will be automatically loaded to TestRecon every time they are executed. By doing this, you no longer need to spend time looking for test results in multiple locations, all your automated results will be in one place! Also, TestRecon provides powerful reporting capabilities and trending that will make the regression review process more efficient, faster and enjoyable.

Sign up for a free trial

The picture below describes how loading from Jenkins using the APIs works

If you are already executing tests using Jenkins you are almost ready to go. All you need to do is install the Jenkins Powershell plugin (Jenkins in Windows) or add a step to run a curl script (Jenkins running in Linux). The scripts are available for download from your account on the TestRecon website.

If you are planning on using Jenkins, you need to complete the following steps first:

1) Have Jenkins installed and running on a local machine or server. Jenkins is very simple to install. Here are some instructions.

2) Create a Jenkins Job. This job will be different depending on the technologies that you are using. For example, you may be using ant, gradle, or maven.

3) Configure the job to pull the test code from source control and execute the tests. The tests results files will be stored in a folder by Jenkins. Here are some simple instructions for ant

4) Configure Jenkins to execute a powershell or curl script to call the TestRecon APIs. In that script, you will specify the location of the test result files and the test suite where the tests belong. The scripts are available for download from your account in the TestRecon website.

Sign up for a free trial

Here are is a sample tutorial from an external website:

 How to schedule Maven Selenium Tests in Jenkins.