k6
k6
k6 runs JavaScript test scripts as load: options (or options.scenarios) set how many virtual users or iterations per second hit the system, the default export is one iteration, and thresholds alone decide whether the run passes (exit 0) or fails (exit 99). That makes most k6 bugs silent: a check() that fails without a threshold on checks, a threshold that passes because its metric got zero samples, a VU ramp that throttles itself as latency rises, or a load generator so busy that it measures itself. k6 is for load and performance; functional end-to-end tests are the e2e-testing skill (e2e-testing SKILL.md), always-on probing is Synthetic Monitoring in the grafana skill (grafana SYNTHETIC-MONITORING.md), and service instrumentation is the observability skill (observability SKILL.md).
Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]
| The job | Read |
|---|---|
Writing a script: the authoring and validation workflow, rules for every script, HTTP, data, lifecycle, custom metrics, handleSummary, HTML, crypto, WebSocket, gRPC, xk6 extensions, jslib pins, k6 x docs |
SCRIPTS.md |
Test types (smoke to breakpoint), executors, open vs closed models, scenarios and --scenario, thresholds, checks and the zero-samples trap, exit codes, automating tests per environment |
LOAD-AND-THRESHOLDS.md |
k6 browser tests: selectors, waits, consent banners, expect(), async checks, screenshots, Web Vitals thresholds, exploring a live site for selectors, validating |
BROWSER.md |
| A full website suite, steps 1 to 4: eliciting workflows, the scaffold, recording with Playwright and har-to-k6, functional protocol and browser tests, assertion libraries | WEBSITE-PERF-TEST.md |
| The website suite, steps 5 to 10: SLO thresholds, hybrid load tests, per-type defaults, the load-generator monitor, local vs cloud and VUh, backend investigation in Grafana, the report | WEBSITE-LOAD-AND-REPORT.md |
Grafana Cloud k6: options.cloud, load zones, cloud run commands, generic automation gates, gcx auth, the API proxy and its quirks, pagination, managing tests, runs and schedules, editing cloud scripts safely, gotchas |
CLOUD.md |
| Reading and investigating cloud runs: the investigation workflow, result vs status vs checks, the v5 metrics API, Loki logs, screenshots, Tempo traces, Insights audits, run reports | CLOUD-RESULTS.md |
| Maintaining existing tests: change control, verification classes, tightening thresholds, migrations, service changes and audits | MAINTENANCE.md |
| Historical run trends, grouping, metric direction, headroom and script/version evidence at inflection points | TRENDS.md |
| Which k6 version a behavior needs: the v2.0.0 migration checklist, v1.7 to v2.3 changes, feature flags, version boundaries in trend data | VERSIONS.md |