Plug Test Studio Into Your
Continuous Integration Environment

Now you can run automated tests around the clock

ts-ci-0

Continuous Integration Defined

The goal of continuous integration (CI) is to prevent integration issues. As the developer team keeps submitting the code they’ve worked on to the source code library, that copy progressively stops to reflect the original source code. Integration conflicts and failures are inevitable once each developer’s branch is integrated back to the trunk.

CI involves integrating early and often (several times a day) so as to avoid that risk. The practice aims to reduce rework and thus reduce development time and expense. Continuous Integration is already considered a best practice and is an essential element of DevOps, Test-Driven Development and Agile development methodologies.

Some of the advantages CI introduces include:

  • Early detection of integration bugs
  • Easy rollback to a bug-free version of the software without debugging
  • Instant feedback on overall impact of introduced changes
  • Faster time to market

Test Automation Advantages in a CI Environment

In addition to the unit tests each developer must run before integrating his branch with the source code repository, CI can be leveraged to implement a process of continuous quality control. Employing a build server, these QA processes run static and dynamic automated tests around the clock to improve the software’s overall quality. It also reduces time to market by replacing the traditional practice of applying quality control after completing all development.

Continuous automated testing benefits include:

  • Better test coverage as tests run around the clock
  • Ship better quality software
  • Free up time and resources for business-critical scenarios
  • Better visibility into overall product health

Integrating Test Studio with Your CI

Test Studio supports continuous integration and delivery by enabling testers to easily automate test cases and schedule those cases to run around the clock, without having to be physically present. You can also schedule tests to run immediately after a build, so that the team understands the state of the build immediately. The build can include the project to be tested, and once the build completes, tests can be set to run automatically.

ts-ci-1

Scheduling Tests to Run 24/7

Leverage the Test Studio test runner to schedule your test lists to start running whenever you want. With Test Studio Runtime installed on your test agents, you’ll be able to leverage the included test runner to execute tests as part of your build process and CI environment.

Once the CI server deploys the new build, it triggers a post-build script that prompts the Test Studio test runner to run the scheduled test lists.

ts-ci-2

Test Results and Reporting

As part of the build automation process, Test Studio test results can be sent to various locations. Test Studio Runtime also includes a powerful command line test runner that allows you to specify whether you’d like results directly sent to Test Studio or to a custom location.

Integrate Test Studio with Any Build Server

Test Studio Build Server Integration

See for Yourself. Let's Get Started.