k6 Load Testing

Execution scope

Confirm exact target, environment, VU/request-rate/duration ceilings, window, stop conditions, downstream effects and test-data cleanup before load. Start at one VU; examples are not permission to stress a public endpoint. Cloud output requires authorization to upload results and incur charges. Checks alone do not fail a k6 run: add checks thresholds for asserted functional correctness. Fixtures must be nonempty and user allocation must match concurrency; modulo reuse can distort auth results.

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use This Skill

• Use when you need to load test HTTP APIs, WebSocket endpoints, or browser scenarios
• Use when setting up performance regression tests in CI/CD
• Use when analyzing system behavior under various load conditions
• Use when comparing performance between code changes
• Use when validating SLA requirements and performance budgets