CI Server Integration

Continuous Integration regularly integrates the individual developer's changes into the main source code control system or repository, performing a new build, verifying the build, and running automated tests against those builds. Continuous integration has many advantages. These include the constant availability of a current build for testing purposes, immediate testing of all changes, and the opportunity for developers to revert the codebase back to a bug-free state when a test fails or a bug is discovered, without wasting time debugging. Learn more about continuous integration at MSDN and Martin Fowler's Continuous Integration.

Thanks to its command line interface, Test Studio for APIs can easily be integrated in most famous CI Servers.

Jenkins Integration

  • Install Telerik Test Studio for APIs on your Jenkins slave or master machine (where you will execute your Jenkins project)
    • You can alternatively just copy the Telerik.ApiTesting.Runner.exe with the whole "runnerconsole" directory as described here.
  • Configure the test execution command (see Command Line Parameters ) - we recommend saving it to a build.cmd file. This is an example:

    Telerik.ApiTesting.Runner.exe test -p "demotests" -f junit -v base-url=http://localhost:5000 -o testresult.xml

  • Execute the build.cmd file as a build step from the Jenkins project

  • Publish JUnit test results report

    Publish JUnit

Other CI Servers

Coming soon ...