bzm-test-analysis

To detect performance regressions in BlazeMeter tests, you compare a specific test run against a resolved baseline. This analysis identifies performance changes and provides actionable recommendations on whether to ship.

You can compare two specific BlazeMeter test executions using run comparison analysis. This evaluates the performance differences between the two runs to help you determine whether the build should be shipped.

Yes, you can analyze BlazeMeter test performance trends by evaluating the execution history of a test over a specified period. This trend analysis helps identify performance degradation or changes over time.

Yes, resolving test executions and checking SLA compliance requires access to the BlazeMeter API. The Skill uses this API connection to retrieve the necessary test performance data for analysis.

You can find the active baseline for a BlazeMeter test using the baseline lookup feature. This resolves and displays the current baseline, which is required for comparing test runs to detect regressions.

The best way to investigate a failed BlazeMeter test is by analyzing error patterns and performance history. This approach identifies regressions, trends, and errors to pinpoint the cause of test failures.