Documentation / Reporting

Reporting

Generate HTML, CSV, TXT, and Markdown outputs with matching layout, ordering, formatting, and built-in failed/correlation report tables across supported languages.

Consistent Report Surface

C#, Java, Python, TypeScript, and JavaScript share the same LoadStrike report structure across HTML, TXT, CSV, and Markdown: matching section order, field names, timestamps, metrics, navigation, plugin tabs, and formatting conventions. TXT keeps plugin-table summaries, CSV and Markdown remain scenario-focused, and plugin hints stay in JSON plus HTML plugin tabs.

HTML Report Tabs

Clickable fixed left-side report sections with pointer-drag panning for Summary, Scenarios, Steps, Status Codes, Failed Responses, plugin tabs, and other report areas that actually have data for the current run. Empty tabs are omitted instead of rendering blank sections. Failed Responses includes a Failed Status Codes table and a Failed and Timed Out Rows table only when those rows exist.

Report Branding

HTML reports render theme-specific LoadStrike logos in a fixed-size header slot (light-logo for light theme, dark-logo for dark theme) so size and alignment remain stable while switching themes.

Theme Toggle

Website and HTML reports support icon-only Light and Dark theme toggles pinned to the top-right corner. Default theme is Light. User preference is persisted per browser via local storage, with fixed logo position across theme changes.

Correlation Tabs

Report includes Ungrouped Corelation Summary and Grouped Correlation Summary tabs only when matched correlation data exists. Both tabs render table-first; ungrouped adds one combined percentile line graph only when percentile points exist, while grouped renders one chart per GatherBy value only for groups that contain percentile data. Correlation chart cards use bounded widths to avoid stretched visuals.

Percentiles

P80, P85, P90, P95, and P99 latencies are included in tables when the underlying data is available. Grouped summary charts include P50 through P99 trend lines for populated groups. Summary renders latency tables and graphs only when those series have data, with overlap-safe percentile rendering so P50, P75, P95, and P99 remain visible even when values are close. Line charts reserve extra top padding so legend labels do not overlap top y-axis values.

Status Percentages

Status Codes tab exposes Percent (overall scope).

LoadStrikeRunner.RegisterScenarios(scenario)
    .WithReportFolder("./reports")
    .WithReportFormats(LoadStrikeReportFormat.Html, LoadStrikeReportFormat.Csv)
    .WithRunnerKey("rkl_your_local_runner_key")
    .Run();

LoadStrikeRunner
    .registerScenarios(scenario)
    .withReportFolder("./reports")
    .withReportFormats("html", "csv", "txt", "md")
    .withReportingInterval(5d)
    .withRunnerKey("rkl_your_local_runner_key")
    .run();

LoadStrikeRunner.register_scenarios(scenario) \
    .with_report_folder("./reports") \
    .with_report_formats("html", "csv", "txt", "md") \
    .with_reporting_interval(5) \
    .with_runner_key("rkl_your_local_runner_key") \
    .run()

await LoadStrikeRunner
  .registerScenarios(scenario)
  .withReportFolder("./reports")
  .withReportFormats("html", "csv", "txt", "md")
  .withReportingInterval(5)
  .withRunnerKey("rkl_your_local_runner_key")
  .run();

await LoadStrikeRunner
  .registerScenarios(scenario)
  .withReportFolder("./reports")
  .withReportFormats("html", "csv", "txt", "md")
  .withReportingInterval(5)
  .withRunnerKey("rkl_your_local_runner_key")
  .run();