Skip to content

Analyzing Results

Running the load test is the easy part. Reading the results is where the work pays off (or doesn't). You need to know what each metric means, what "normal" looks like for the system you're testing, which transactions slowed down first, which user-level threshold the system started to break at, and which server-side resource ran out at that moment. Done well, the analysis hands the development team a small, specific list of things to fix. Done poorly, it hands them a two-hundred-page report that nobody reads.

In v7.0 the primary analysis surface is the Embedded Analytics Dashboard, which opens in the application when you double-click a test result. It's interactive, drills down by page and by virtual user level, and correlates response-time degradation with server metrics automatically. The legacy in-app reports still exist for the workflows the dashboard doesn't cover yet, mainly errors-by-transaction inspection.

The AI assistant lives inside this section heavily, because analysis is where it pays off most. It can summarize a result, identify the slowest transactions, find the user level where things broke, and write a narrative report you can hand to stakeholders.

In This Section

  • Results Overview: The Analytics Dashboard layout and the Results View. What each panel is for and when to use each.
  • Understanding Metrics: Response time, throughput, errors, percentiles, user-level breakdowns. What each metric measures and how to interpret it.
  • Reports: Legacy in-app reports (embedded with dropdown navigation) and how they differ from the new AI-generated DOCX reports.
  • Performance Workflow: A repeatable analysis sequence: overview, hot pages, user-level threshold, server correlation, narrative.
  • Analytics Dashboard: Detailed reference for the dashboard's charts, filters, and drill-downs.
  • Identifying Bottlenecks: Server-side, network, application, database. How to figure out which one a slowdown actually points at, instead of guessing.
  • Troubleshooting: Common analysis problems: missing data, suspicious results, dashboard issues.

If you're starting from a fresh result, double-click it to open the Analytics Dashboard and walk through Performance Workflow. Once you know what you're looking at, the rest of this section is reference material for the specific questions that come up.