comparison-report-workflow

To compare multiple performance test runs side by side, provide 2-5 completed run IDs. The workflow validates prerequisites, generates consolidated comparison reports, and creates CPU and memory charts for quick insight into performance trends.

Yes, you can publish performance testing comparison reports to Confluence. By providing optional Confluence publishing details alongside your run IDs, the workflow publishes the generated reports and charts directly using Confluence MCP tooling.

Generating a performance test comparison report requires 2-5 completed end-to-end test run IDs. The workflow validates prerequisites across all runs to ensure completed E2E workflows before generating unified reports and visualization charts.

CPU and memory charts help analyze performance testing bottlenecks by visualizing resource utilization trends across multiple test runs. This side-by-side data visualization reveals performance variations and informs potential system optimizations.

The best way to automate end-to-end performance test analysis is using a workflow that consolidates multiple run results. This approach validates completed runs, generates unified comparison reports, and optionally publishes findings to Confluence for team visibility.