Class BowireK6Summary
- Namespace
- Kuestenlogik.Bowire.Benchmarking
- Assembly
- Kuestenlogik.Bowire.Benchmarking.dll
Renders a run as k6-summary JSON (#234 shape, #360 thresholds).
The metric block mirrors what the workbench rail already exports
(http_req_duration / http_reqs / iterations /
iteration_duration / http_req_failed / checks), so a
dashboard that ingests a run exported from the UI ingests one written by
bowire bench run without a second code path.
Thresholds ride along the way k6 itself reports them: keyed by their
source text inside the metric they constrain, each with an ok
flag. That is what makes "downstream tooling agrees" true rather than
aspirational — a CI dashboard reading k6 summaries finds Bowire's
budgets exactly where it looks for k6's.
public static class BowireK6Summary
- Inheritance
-
BowireK6Summary
- Inherited Members
Methods
Build(BowireBenchmarkStats, IReadOnlyList<BowireThresholdResult>?)
Build the summary document for stats, annotating
each metric with any threshold that constrains it.
public static JsonObject Build(BowireBenchmarkStats stats, IReadOnlyList<BowireThresholdResult>? thresholds = null)
Parameters
statsBowireBenchmarkStatsthresholdsIReadOnlyList<BowireThresholdResult>
Returns
Render(BowireBenchmarkStats, IReadOnlyList<BowireThresholdResult>?)
Serialise Build(BowireBenchmarkStats, IReadOnlyList<BowireThresholdResult>?)'s document.
public static string Render(BowireBenchmarkStats stats, IReadOnlyList<BowireThresholdResult>? thresholds = null)
Parameters
statsBowireBenchmarkStatsthresholdsIReadOnlyList<BowireThresholdResult>