Describes how the framework is handling results of performance testing

Performance test results storage

To simplify results analysis and support Continuous Performance Testing, Jagger framework is storing measured parameters

Results are stored in MySQL or H2 database. You can configure storage via Jagger properties

Every execution of the load scenario corresponds to a separate test session in the test results database. For every test session framework is storing:

general info
- when test session was started and
- what was the configuration of the load scenario
- user tags. You can mark every load scenario execution with tags to sort and search your test results later
- user comments. You can add additional user comments to every test session
information about executed load tests
- when load test was started
- what load profile was used
- what termination strategy was used
detailed tests results
- metrics id, display name, aggregated value(s), detailed results. You can configure what results will be stored for different metrics
decisions
- decision per metric, test, test group, scenario
test environment information
- information about every node, participating in the test: CPU info, java version, OS info, available system memory

Test results access

You can access test results via multiple channels:

Web UI - instrument for results analysis, presentation and sharing
JaaS REST API - access to the test result and report generation
Reporting - pdf report generation per particular test session
SessionInfoService - write access to the test results from the source code of your test project. You can add comments (e.g. some additional description of your test session) and mark test sessions with Tags
DataService - access to the test results from the source code of your test project