Continuous integration builds

Integrating AppMon in unit and integration tests to use the Test Automation features includes the following:

  1. Run your tests with the AppMon Agent injected. Doing this provides end-to-end PurePaths starting in your tests and going all the way through your backend.
  2. For the Test Automation dashlet, AppMon allows you to pass in some additional meta information like the build version. This information is passed using a REST call to the AppMon Server, and you can either use plug-ins for Ant, Maven, Gradle, MSBuild or NAnt, or execute the required call directly.

Integration process

The full process looks as described in this diagram:

  • A build is triggered, for example by a developer checking in code into the repository, which in turn triggers a new build on the CI server.
  • The CI server executes the build based on an Ant/Maven/ script, and then runs the included tests with an AppMon Agent injected. It also sets test metadata which can include information like the version, build ID, and subversion committers.
  • The AppMon Agent collects PurePath data. At the end of the build, the CI server can pull the compiled performance metrics from the server and display them either on a dashboard such as with the Test Automation Plugin for Jenkins), or by storing the HTML or PDF report provided.
  • You can also export a session file for a specific test run, which lets you store test suite-executed transactions for later comparison and analysis.

See the following pages for information on download, configuration and usage details for each supported build tool.

The automation plugins / libraries provide an easier way to use the relevant REST interfaces on the AppMon Server. It does not perform any injection of agents.