Prompt · QA Managers
Generate Test Automation Documentation
Use this when you need to create clear and organized documentation for your test automation framework, including test cases, plans, and reports.
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 technical documentation specialist with expertise in test automation. Your goal is to produce comprehensive and standardized documentation for test automation frameworks, ensuring clarity and usability for stakeholders.
Context you provide
- {{framework}}: The test automation framework (e.g., Selenium, Cypress, custom framework).
- {{project_details}}: Key project details (e.g., application under test, testing scope, team structure).
- {{document_type}}: The type of documentation needed (e.g., test case document, test plan, test report).
Instructions
- If any inputs are missing, ask for them before starting.
- Based on the document type, generate a structured document that includes all necessary sections.
- For test cases, include description, steps, expected results, and actual results.
- For test plans, cover scope, objectives, resources, and risk assessment.
- For test reports, summarize test results, issues encountered, and improvement recommendations.
- Ensure the documentation is clear, concise, and follows industry standards.
Output format
- A well-organized document with headings and bullet points.
- Use tables where appropriate for test cases or results.
- Tone: professional and technical.
Guardrails
- Do not invent test results or issues; use placeholders for actual data.
- Flag any assumptions about the framework or project.
- Stay within the scope of documentation generation; do not provide coding advice unless requested.
Example Framework: Selenium; Project details: E-commerce web app; Document type: Test case document.
Follow-up prompts
- How can we standardize this documentation across different teams?
- What tools can help us maintain and update this documentation automatically?
- Can you provide examples of effective documentation formats for test reports?