Although it has always been possible to integrate AscentialTest with Jenkins manually, the new AscentialTest Jenkins Plugin makes that integration much easier to accomplish.
The Plugin configures and runs the AscentialTest command lines to execute tests and generate reports.
It also makes use of an existing Jenkins plugin to create a bar chart of pass/fail/blocked/not-run history.
The AscentialTest plugin can be installed from the Jenkin’s Plug-in Manager like any other plug-in.
The Plugin panels indicate missing required fields and provide ‘help’, using standard Jenkins method. If the user clicks on the icon, a help panel will display to describe the associated parameter.
In addition to running the command lines to execute tests and generate AscentialTest Test Set reports, the plug-in also generate results data that can be graphed using other Jenkins Plug-ins.
If you install the ‘Plot’ plugin, you can add a post-build action to plot the data that is exported at the completion of each AscentialTest run.
To assist you with configuring the Plot plug-in, the following example is provided:
After inputting all of the AscentialTest Plug-in parameters, click ‘Save’ to return to the Jenkins Project Workspace.
Then click the ‘Build Now’ link to execute tests and generate results.
Based on whatever triggers are set in the Jenkins project, the test will either begin to run immediately or when the trigger events occur.
Once the run is complete, the reports selected in the new plugin panel will be available in the ‘Report Path’ folder set in the primary plug-in panel. If you selected the Jenkins Workspace as the ‘Report Path’ the reports can be opened directly from the Jenkins Workspace by double-clicking.
In addition to the standard AscentialTest reports that can be selected from the primary plug-in panel:
If you have installed the ‘Plots’ plug-in, you can click on ‘Plots’ to generate a bar chart of the pass/fail history like the one pictured below:
This report provides a good way to compare the results of Test Set execution over time.
The AscentialTest Plug-in uses environment variables that must be injected into the Jenkins build environment.
The ‘Environment Injector’ Plug-in or comparable must be installed prior to executing tests.
Depending on your Jenkins configuration, you may find that UA Server runs in the background and may not be able to hook the target application.
This is more likely to occur when executing individual Tests than with Test Sets.
The problem is caused because the background UA Server does not have the target application extension enabled.
Here are the steps to resolve this issue:
If you have any questions about the AscentialTest Jenkins Plug-in,
please contact Novalys Support at email@example.com. We are here to answer your questions.