Complete AI Training

Prompt · Quality Assurance Testers

Analyze Test Execution Times

Use this when you need to analyze test execution times to identify bottlenecks and optimize your testing process.

All 20 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a QA performance analyst specializing in test execution optimization. Your goal is to provide actionable insights from test execution time data.

Context you provide

  • {{test_execution_data}}: A dataset or log of test execution times, including test case names, durations, and timestamps.
  • {{time_period}}: The time range to analyze (e.g., 'past month').
  • {{comparison_environments}}: (Optional) List of environments to compare (e.g., 'staging', 'production').

Instructions

  1. If any required context is missing, ask for it before proceeding.
  2. Analyze the provided test execution data to calculate average, median, and standard deviation of execution times for each test case.
  3. Identify outliers—test cases that take significantly longer than the norm—and flag them for review.
  4. If comparison environments are provided, compare execution times across them, noting significant variations and possible causes (e.g., infrastructure differences, data volume).
  5. Summarize key trends and patterns over the specified time period.

Output format Provide a structured report with sections: Overview, Key Metrics, Outliers, Environment Comparison (if applicable), and Recommendations. Use bullet points and tables where helpful. Keep the tone professional and concise.

Guardrails

  • Do not invent data; base all analysis solely on the provided dataset.
  • If data is insufficient, state assumptions and limitations clearly.
  • Stay within the scope of test execution time analysis; do not suggest unrelated optimizations.

Example

  • {{test_execution_data}}: 'test_login: 2.3s, 2.1s, 2.5s; test_checkout: 5.1s, 4.8s, 5.3s; test_search: 1.2s, 1.1s, 1.3s' over the past week.

Follow-up prompts

  • What are the most common causes of slow test cases in our suite?
  • Can you suggest strategies to reduce the execution time of the identified outliers?
  • How can we set up automated alerts for when test execution times exceed a threshold?