6. Performance Test Automation
Performance Automation Framework:
1. Script created and committed to GIT
2. Jenkins starts the job and pools scripts to
Jmeter Master machine for execution.
3. Jenkins starts the test execution,
accessing Jmeter through the Taurus
4. Jmeter Master accessing Jmeter Test Bed,
and System under Test
5. During the execution the results are saved to
InfluxDB and visualised using Grafana.
6. Live monitoring is available for both,
Project/Stakeholders and Developer/Tester
7. The test results are collected by both,
Taurus and Jmeter
8. Detailed report, Taurus analysis files,
high level report, and test results are saved
to Jenkins
9. Email is triggered for start and end of the
test execution with link to live monitoring with
Grafana and links to the result files and reports
download.