performance-test-designlisted

Design performance test cases and test data specifications for an entire system — from raw system documentation (BRD, FRD, use cases, NFR/SLA docs, architecture docs) to implementer-ready Performance Test Case Specifications — without depending on any specific load-testing tool (JMeter, k6, Gatling, LoadRunner). Use whenever the user needs to discover which Operational Profiles a system needs tested, design load/stress/spike/soak/scalability/volume test scenarios, define workload models, calculate virtual users and throughput, or produce test data specifications from requirements. Use when the user mentions "performance test design", "load test scenario", "workload model", "operational profile", or "test data for performance testing", or asks how to design performance test cases from requirements — even without naming a specific technique. Produces design documents and specifications only; does NOT write or generate executable test scripts/code for any tool — that remains a separate implementation step.
phatnguyen975/performance-test-design · ★ 0 · Testing & QA · score 70

Install: claude install-skill phatnguyen975/performance-test-design

# Performance Test Design Skill ## Overview This skill takes a system's requirements documentation and turns it into a complete set of implementer-ready **Performance Test Case Specifications** — one per Operational Profile the system needs tested — following the ISTQB Certified Tester Performance Testing (CT-PT) syllabus process, extended with real-world workload-modeling practice beyond what the syllabus covers at a summary level. The process has exactly **two phases**: 1. **Phase 1 — Operational Profile Discovery:** Read the system's documentation once, and produce a reviewed, approved list of every Operational Profile the system needs performance-tested. 2. **Phase 2 — Per-Profile Test Case Design:** For each approved profile, in order, run it through four dependent steps (profile analysis → load profile design → throughput/concurrency analysis → test case specification) to produce that profile's complete design, then pause for human review before moving to the next profile. This skill is the **design layer** — it stops at the specification. It never writes JMeter/k6/Gatling/LoadRunner code, and it never picks a tool. ## When to Use - Starting performance test design for a system (or a release/module of one) from its requirements documentation, before any scripting begins. - Discovering and enumerating the full set of Operational Profiles a system needs tested — not just designing one test case in isolation. - Translating NFRs/SLAs into concrete, measurable, per-tr