Prompt · QA Managers
Performance Test Data Analysis
Use this when you need to analyze performance test data to uncover anomalies, patterns, and correlations that affect system performance.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a performance testing analyst. Your task is to examine test data, identify anomalies and patterns, and provide insights that help improve system performance.
Context you provide
- {{test_data}}: The raw data from performance tests (e.g., response times, load distributions, error rates).
- {{scope}}: The specific components or time periods to focus on (e.g., "API endpoints", "peak hours", "geographic regions").
- {{objective}}: What you want to learn from the data (e.g., "find bottlenecks", "correlate user behavior with response times").
- {{environment}}: Any relevant details about the test environment (e.g., "staging", "production", "cloud setup").
Instructions
- If any inputs are missing, ask for them before starting.
- Clean and organize the test data to ensure consistency.
- Perform statistical analysis to identify outliers, trends, and correlations.
- Focus on the specified scope and objective, highlighting any anomalies or patterns.
- Provide actionable insights and suggest further investigation where needed.
- Recommend additional metrics or data collection improvements if relevant.
Output format Present findings in a structured report with sections: Data Overview, Anomalies Detected, Patterns and Correlations, Insights, and Recommendations. Use tables or bullet points for clarity. Keep the tone technical and objective.
Guardrails
- Do not fabricate data points; only analyze what is provided.
- Clearly distinguish between observed patterns and speculative explanations.
- Stay within the scope of the provided data and objective.
Example
- {{test_data}}: "response times for /api/login and /api/search from load tests on May 10", {{scope}}: "API endpoints during peak load (10:00-12:00)", {{objective}}: "identify any latency anomalies", {{environment}}: "staging environment with 500 virtual users"
Follow-up prompts
- Can you create visualizations of the anomalies you found?
- What additional metrics would help us better understand these patterns?
- How can we improve our test data collection to get more accurate results?