View Apica Loadtest on the plugin site for more information.
The plugin enables Apica Loadtest customers to run automatic load tests as part of a Jenkins build process.
Build runner setup
The plugin is a build runner and can be added to a project on the project's configuration page:
The Apica load test plugin is available in the "Add build step" list:
You'll then see the build runner options:
Select your environment and set the required entries: the authentication token, the preset name and the load test scenario file name. You can use the Test settings button to test your inputs. If all properties are correct then you'll see a confirmation:
Here are some example error messages in case some property is not correct:
- Exception while checking preset: The authentication ticket is not well formatted.
- No such preset found: short test2
- Load test file name must be either a .class or .zip file.
- No such load test file found: cldemo_start2.class
Note that Jenkins won't block the user from saving a build runner despite validation errors. The settings are additionally rechecked before a test starts.
It's possible to add thresholds to the test. If the threshold is broken then the test can be marked as "failed":
Save your setup:
Running the Apica build runner
You can start the build runner like you would start any other runner in Jenkins. The simplest way is to start a build on the UI:
You can monitor the build progress by clicking on the build number and opening the Console output link:
You can check the detailed build log for messages. They are similar to what people see in the live stats window of LTP:
The runner checks the job status every 10 seconds at present.
At the end of the job the log shows some basic statistics and the thresholds are evaluated:
Refresh the build page after a successful job. You'll see two links on the left hand panel:
Apica load test summary presents the key statistics in tabular format:
The Apica load test trends tab shows a custom CI page in an iframe: