Icon

Comments have been closed on this page. Please use AppMon & UEM Open Q & A forum for questions about this plugin.

Overview

 

The Jenkins plugin pulls Test Automation data from the dynaTrace Server and displays it through charts and tables on the project and build level.
Icon

This page contains the documentation for the version 1.x of the plug-in. For latest version of the Plug-in, see Test Automation Plugin for Jenkins.

Name and Version

Test Automation Plugin for Jenkins

Compatible with

dynaTrace 5.x, dynaTrace 6

Author

Wolfgang Gottesheim

License

Dynatrace BSD

Support Level

Not Supported

Download

  File Modified
PNG File configuration.png May 27, 2016 by Sonja Chevre
PNG File dT Test Automation_noPerfTests.png May 27, 2016 by Sonja Chevre
File dynatrace-dashboard_1.0.20.hpi Fixed missing "invalidated" status for test May 27, 2016 by Sonja Chevre
File dynatrace-dashboard_1.0.4.hpi May 27, 2016 by Sonja Chevre
File dynatrace-dashboard_1.0.5.hpi Fixed version to check for missing "unit" field in browser tests May 27, 2016 by Sonja Chevre
PNG File icon.png May 27, 2016 by Sonja Chevre
PNG File Jenkins.PNG May 27, 2016 by Sonja Chevre
PNG File reporting_limit.png May 27, 2016 by Sonja Chevre
PNG File testAutomation-BuildLevel.png May 27, 2016 by Sonja Chevre
PNG File testAutomation-DashboardLevel.png May 27, 2016 by Sonja Chevre
PNG File testAutomation-ProjectLevel.png May 27, 2016 by Sonja Chevre

Source Codehttps://github.com/jenkinsci/dynatrace-plugin/ and https://wiki.jenkins-ci.org/display/JENKINS/Dynatrace+Plugin

Description

 

Changelog
  • 1.0.4 (Jan 28, 2014): fixed a NullPointerException in parsing the XML dashboard report
  • 1.0.3 (Jan 27, 2014): introduced switch to suppress logging of test results pulled from the dynaTrace server

Installation

Install the plugin through the Jenkins interface: Manage Jenkins -> Manage Plugins -> Available -> Search for "Dynatrace" in the list and install.

Usage

The Jenkins plugin pulls Test Automation data from the dynaTrace Server and displays it through charts and tables on the project and build level. In order to do this, it is designed as a "Post-Build Action" and has to know

  • how to connect to the dynaTrace Server, and
  • how to identify which tests where executed in a build.

In order to do this, we have two prerequisites that have be fulfilled:

  • On the dynaTrace Server, a dashboard that contains the Test Automation dashlet has be created. This dashboard will be queried through the REST interface from the Jenkins server, so the dynaTrace Server REST interface has to be accessible from the machine running Jenkins.

    Icon

    The dashboard report is limited to the first 100 tests in the Test Automation dashlet by default. If you have more than 100 tests, please adjust the "Maximum Number of lines per table" in the Reporting section of the dashlet properties accordingly.

  • In the build that is executed, the DtSetTestInformation call to the dynaTrace Server has set the BUILD_ID provided by Jenkins as the build number. This field is used to identify which tests were executed in a build.


Configuration

To set it up, you can add the "dynaTrace Test Automation" action as a post-build action to your build:

Here you can enter the connection details as well as the name of the dashboard containing the Test Automation dashlet, and you can test the connection.

In the advanced settings, you have the following options:

  • You can change if the build result from the dynaTrace Server should also affect the Jenkins build result - if this is enabled, tests that are considered as volatile or failed (from a functional or performance perspective) by dynaTrace will cause the Jenkins build to be unstable or fail. By default, this feature is enabled
  • Depending on the dynaTrace Server load and the volume of tests, it might take a while until the test results are available through the REST interface. By default, the Jenkins plugin will try to get data 6 times, 10 seconds apart. If necessary, you can increase the number of tries here. Please keep in mind that this increases the build duration.

dynaTrace Test Information

The Jenkins plugin uses the BUILD_ID field as a means to identify which tests where executed in a test. Consequently, your build script has to use this BUILD_ID as the buildNumber for the DtSetTestInformation call, and of course has to execute its tests with a dynaTrace Agent being injected. This can be done in several ways:

Ant

We import environment variables as properties and use it then to tag the build:

Maven

For a Maven build, you can call the appropriate goal directly from the build configuration ("Goals and options" field):

 

Screenshots

  • No labels