Test Planning & Strategy

Act as a senior performance engineer. Generate a comprehensive performance test strategy document for a [REST API / web application / microservices system] that handles [describe the system briefly]. 

Include:
- Objectives and scope
- Test types required (load, stress, soak, spike, breakpoint)
- Entry and exit criteria for each test type
- SLA targets (response time, throughput, error rate)
- Environment and infrastructure requirements
- Risks and mitigation strategies
- Tools and technology stack recommendation
- Roles and responsibilities

Format as a professional document with sections and tables where appropriate.

I have the following business requirements for my application:
[Paste business requirements or NFRs here]

Convert these into measurable SLA targets for performance testing. Define:
- p50, p90, p95, p99 response time thresholds
- Throughput (requests per second / transactions per minute)
- Error rate thresholds
- Apdex score targets
- Resource utilization ceilings (CPU, memory, connections)

Explain the rationale behind each threshold.

I am testing [application name] which has the following user journeys:
[List top 3–5 user journeys]

Help me define the performance test scope:
- Which transactions to include / exclude and why
- Prioritization by business criticality
- Estimated transaction mix (%)
- Think time recommendations
- Pacing strategy
- Entry and exit criteria

My application is [describe: e-commerce / banking API / streaming platform / etc.].
Expected peak concurrent users: [N]
Expected peak RPS: [N]
Key concern: [latency / throughput / stability / scalability]

Which performance test types should I run and in what order? For each test type, provide:
- Goal
- Duration
- VU ramp-up profile
- Pass/fail criteria
- What to watch for

Review the following Non-Functional Requirements (NFRs) for completeness and testability:
[Paste NFR document or list]

For each requirement, assess:
- Is it measurable? If not, suggest how to make it measurable.
- Is it testable with JMeter / k6?
- Are there gaps or ambiguities?
- Recommended SLA thresholds based on industry standards.

Output as a table: NFR | Measurable | Testable | Gap | Recommendation