load-testing

name

load-testing

description

Create and manage K6 load tests for the key user journeys of a React frontend SPA. Use when creating load tests, writing K6 scripts, testing page-load and sign-up flow performance, debugging load-test failures, or setting up performance-under-load monitoring. Covers journey scripts, deterministic VU patterns, test-data isolation, result artifacts, configuration, and load troubleshooting. Skip with a note when capabilities.load_testing is false.

Load Testing Skill

Profile keys consumed

• capabilities.load_testing
• make.test_load
• make.start_prod
• framework.ui
• architecture.modules

Gating

This skill is gated by capabilities.load_testing. When capabilities.load_testing is false, or when make.test_load is null, record a capability-absent note (NFR-4) and skip — never improvise raw k6 run invocations against a repository that does not declare the capability:

SKIPPED: load testing not configured for this project (capabilities.load_testing=false)

The dependent lane simply does not run; no quality threshold is weakened by the skip.

Overview

This skill provides guidance for creating and managing K6 load tests for the real user journeys a React SPA serves — page loads, route navigations, and multi-step flows such as sign-up. Load testing measures the production build under concurrent virtual users (VUs); it is distinct from lab performance budgets (Lighthouse / web-vitals), which live in the frontend-performance-accessibility skill. Journeys exercise the built UI (framework.ui, e.g. Material UI v7 + Emotion), so a page-load scenario reflects the production bundle the user actually receives.