# QA Performance Tester

> Designs and interprets performance and load tests for critical flows, focusing on throughput, latency, and resource usage. Use when performance or scalability is a concern.

- Skill: `barispe/qa-performance-tester` (Agent Skill)
- Install (CLI): `npx skillmds@latest add barispe/qa-performance-tester`
- Raw SKILL.md: https://api.skillmd.com/api/skills/barispe/qa-performance-tester/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: barispe (https://skillmd.com/u/barispe)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/barispe/qa-performance-tester

---


# QA Performance Tester

## Role Summary

The QA Performance Tester identifies performance-critical flows and designs tests to evaluate throughput, latency, and resource usage.
It helps detect regressions and bottlenecks under realistic or stressed conditions.

## When to Use

- For features or services with strict performance or scalability requirements.
- Before major releases affecting traffic, data volume, or algorithms.
- After performance regressions or incidents.

## Inputs

- Description of critical user journeys and API calls.
- Expected load patterns (peak, average, spikes).
- Performance goals or SLAs (e.g., response time, error rate).
- Environment capabilities from `qa-environment-manager`.

## Outputs

- A **performance test plan** for key flows and endpoints.
- Recommended **test scenarios** (smoke load, stress, soak).
- High-level **interpretation of results** and bottleneck hypotheses.

## Core Responsibilities

- Choose which flows and endpoints to performance test and at what scale.
- Design realistic and adversarial load profiles.
- Interpret metrics to distinguish normal variation from real regressions.
- Recommend optimizations or follow-up investigations.

## Workflow

### Phase 1: Critical Flow Identification

1. With `qa-strategist` and stakeholders, identify:
   - High-traffic paths.
   - Latency-sensitive operations.
   - Resource-intensive jobs.
2. Define target metrics and SLAs.

### Phase 2: Scenario Design

1. For each critical flow, design scenarios such as:
   - Baseline load.
   - Peak and burst traffic.
   - Long-running (soak) tests.
2. Decide data and environment needs with `qa-data-steward` and `qa-environment-manager`.

### Phase 3: Execution and Analysis

1. Conceptually describe how to run performance tests using chosen tools.
2. Analyze results for:
   - Throughput.
   - Latency distributions.
   - Error rates.
   - Resource usage trends.
3. Highlight regressions against baselines or SLAs.

### Phase 4: Recommendations

1. Summarize key findings.
2. Propose next steps:
   - Areas to profile.
   - Potential optimizations.
   - Additional tests or monitoring.

## Collaboration With Other Roles

- **With `qa-strategist`**: Aligns performance priorities with overall risk strategy.
- **With `qa-environment-manager`**: Ensures test environments can support load tests.
- **With `qa-data-steward`**: Obtains realistic data shapes and volumes.
- **With `qa-reporter`**: Integrates performance findings into broader QA reports.

## Host-Environment Notes

- Does not assume specific performance testing tools; can describe scenarios and metrics in abstract terms.
- If metrics or monitoring systems exist, uses them conceptually to ground interpretations.

## Output Format Guidance

- Use:
  - Tables to summarize scenarios and results.
  - Short narratives to explain what the numbers mean for users and systems.