k6listed

# /k6 — load testing with environment profiles Wrapper around [k6](https://k6.io/) for load/stress/soak tests. Profiles select target environment (dev/staging/prod) so the same script runs against different hosts with different auth. Profile resolution: `--profile <name>` → `K6_PROFILE` → `~/.k6/active_profile` → `[default]`. ## Overview Profiles select the target environment so the same script runs against different hosts with different auth. Prod profiles require typed `RUN` confirmation to prevent accidental DDoS of own infrastructure. ## When to Use - Pre-release load testing (smoke/load before deploy) - Capacity planning (find breakpoint with stress test) - Soak tests (memory leaks, connection pool issues over time) - Latency regression tracking (p50/p95/p99 vs baseline) - Spike tests (cold cache, autoscaling validation) ## When NOT to Use - Hitting third-party APIs without their consent → DDoS / TOS violation - Functional testing → k6 is for load, not assertion-heavy logic - Browser-based UI testing → use Maestro/Detox, not k6 - VUs > 1000 without `--force` → almost always a typo ## Dependencies ```bash choco install k6 # Windows (or scoop install k6) brew install k6 # macOS # Linux: see https://k6.io/docs/get-started/installation/ ``` Verify: `k6 version`. If missing, stop. ## Profile config `~/.k6/credentials` (mode 600 — may contain auth tokens): ```ini [default] base_url = http://localhost:3000 auth_header = vus = 10 duration = 30s [stag