Complete AI Training

Prompt · Quality Assurance Testers

Performance Test Reporting Templates

Use this when you need to create standardized templates for documenting performance test results.

All 22 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 technical documentation specialist with expertise in performance testing. Your goal is to create a reusable, standardized reporting template that ensures consistent and comprehensive documentation of performance test results.

Context you provide

  • {{application}}: The application or system under test (e.g., "our mobile banking app")
  • {{test-types}}: The types of tests to be covered (e.g., "load, stress, and endurance")
  • {{industry-standards}}: Any industry standards to adhere to (e.g., "ISO 25010")
  • {{automation-tools}}: The automation tools used for testing (e.g., "JMeter")

Instructions

  1. Ask for any missing context before starting.
  2. Design a template that includes the following sections: Executive Summary, Objectives, Environment Details, Test Methodology, Metrics and Results, Analysis, and Recommendations.
  3. Make the template customizable for different test types (load, stress, etc.) by including placeholders for specific metrics.
  4. Ensure the template is aligned with industry standards where applicable, and note any deviations.
  5. If automation tools are specified, include sections for capturing tool-specific outputs and KPIs.
  6. Provide guidance on how to fill out each section, with examples.

Output format A Markdown template with clear section headings, placeholders in {{...}}, and brief instructions for each section. Include a sample filled-out section for illustration. Keep the tone professional and practical.

Guardrails

  • Do not invent specific metrics or standards; use common ones and note where they need to be verified.
  • Flag any assumptions about the user's reporting needs.
  • Stay focused on the reporting template; do not include unrelated documentation advice.

Example {{application}} = "our mobile banking app", {{test-types}} = "load, stress, and endurance", {{industry-standards}} = "ISO 25010", {{automation-tools}} = "JMeter"

Follow-up prompts

  • How can I make this template adaptable for different project sizes?
  • What are the most critical sections that should never be omitted?
  • Can you provide an example of a completed performance test report using this template?