Skip to content

Manual performance test cases, case ID on every k6 run - #4

Merged
niranjankagri merged 1 commit into
mainfrom
docs/manual-test-cases
Oct 30, 2026
Merged

niranjankagri merged 1 commit into
mainfrom
docs/manual-test-cases

Conversation

@niranjankagri

Copy link
Copy Markdown
Owner

What

  • docs/manual-test-cases.md: smoke TC-301, load TC-302, stress TC-303, spike TC-304, soak TC-305: goal, workload, pass criteria, what to watch; SLO table.
  • Each script: tags: { testid: 'TC-30N' } on every metric, and summaryFor('<name>', 'TC-30N') so the ID appears in the Markdown summary heading and the JUnit suite name.
  • Unchanged on purpose: report file names (reports/<test>-*.{json,md,xml}), JUnit classnames and threshold test-case names, so CI artifacts and collected results keep working.

Checked locally

npm run lint (eslint + prettier). Smoke runs in CI.

🤖 Generated with Claude Code

docs/manual-test-cases.md: TC-301..305 (smoke, load, stress, spike, soak) with goal,
workload, pass criteria and what to watch. Each script tags its metrics with testid and
passes the ID to summaryFor(), which puts it in the Markdown heading and the JUnit suite
name; report file names, classnames and threshold names are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@niranjankagri
niranjankagri merged commit d68a490 into main Oct 30, 2026
14 checks passed
@niranjankagri
niranjankagri deleted the docs/manual-test-cases branch October 30, 2026 06:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant