Milestones
List view
S3 — k6 output is not recognised by galaxio report.
No due date•0/1 issues closedS3 — galaxio report recognises Gatling only, so a JMeter run cannot be summarised or checked with the same command.
No due date•0/1 issues closedS3 — A finished run is reported as one set of figures for its whole span, so a run whose throughput collapsed halfway prints the same averages as a healthy one, and no series can be drawn from an archived run.
No due date•0/1 issues closedS3 — Verdicts exist only as an exit code and console text; nothing writes them in the ecosystem's own format, so no other tool can consume them.
No due date•0/1 issues closedS3 — Gatling no longer writes assertions.xml, so CI systems that consumed a JUnit file from a load test have nothing to read. Whether verdicts should be published in Gatling's retired schema at all is the question.
No due date•0/1 issues closedS2 — A RequirementSet describes what a run must satisfy, but nothing checks a finished run against it, so requirements stay prose in CI.
No due date•0/1 issues closedS3 — Gatling 3.13.5 stopped generating stats.json and global_stats.json, and every tool that globbed them, the Jenkins plugin included, silently sees no run. Whether to keep a dead schema alive is a decision, and refusing is a legitimate outcome.
No due date•22/23 issues closed