The breakdown structure contains your test script in a visual way; most of the components (thresholds, groups, requests...) that you've added in your script will be represented in the same order in the breakdown. This section will help you to:
- Find failing errors: checks, thresholds and requests.
- Find the slowest/fastest groups and requests.
- Visualize custom metrics.
- Drilling down check, custom and request metrics.
In the top left of the breakdown you'll find a `status filter`. This filter will let you show or hide passed and failed items and the selected filter will only affect the breakdown and nothing else. The error filter will be applied to:
Moving down in the breakdown you'll see your added groups, checks and requests. To the left of each item in the breakdown you can see the status represented by a red or green border together with a summary of the error rate.
For a group the error rate will be the number of passed or failed checks and requests in that group(including any nested sub groups). Checks and requests will display a percentage of the success rate.
Finding slowest/fastest groups and requests
To the right of each group or request you'll find an aggregated value for the `response time` for that item. This value is based on all requests in that group and will respect the aggregation method selected previously.
To find the slowest(or fastest one) simply click the `Load time` column header and it will sort the breakdown on descending `response time`.
Click the header again to change to ascending order.
When you find a group, URL or check that you want to see more information about click the row to expand the metrics section for that resource. If you want to see metrics aggregated for a group you'll find them in the `more` menu to the right of the `load time`.
For a URL you can see the status distribution at the top of the expanded area and beneath you'll find a chart with metrics for that URL. Read more about k6 HTTP metrics.
When you find something interesting that you want to compare with other metrics or keep for later you can add the metric to the analysis panel. Metrics added to the analysis panel will be persisted if you leave the results page and come back later.
See more: Insights: analysis view.
Group metrics are aggregated metrics based on all requests in that group. Because they behave as a request aggregation, you can visualize the same type of charts than a URL metric.
The metric chart for a check contains passes and failures. This will give you a good overview of when a check is failing during the test run.
Custom metrics and thresholds
Custom metrics and thresholds created in your test script will be available to the root group in the breakdown. You could visualize the metric values (based on the current aggregation) and metric percentiles.
See next: Insights: analysis view.