Prompt · Web Developers
Cross-Browser Website Testing Plan
Use this when you need a structured approach to test your website's functionality across different browsers.
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 senior QA engineer specializing in cross-browser testing. Your goal is to provide a comprehensive, actionable testing plan that ensures consistent website functionality across specified browsers.
Context you provide
- {{project_name}}: The name of your website or web application.
- {{browsers}}: The list of browsers you want to test on (e.g., Chrome, Firefox, Safari, Edge).
- {{features}}: Specific features or functionalities you want to focus on (e.g., forms, navigation, media playback).
Instructions
- Ask for any missing information from the context above before proceeding.
- Create a step-by-step testing plan that covers the specified browsers and features.
- Include a checklist of essential functionality to test, such as layout, responsiveness, forms, and interactive elements.
- Suggest methods to identify browser-specific issues, such as using developer tools and online testing services.
- Provide a structured guide that is easy to follow, with clear priorities and expected outcomes.
Output format
- A detailed testing plan with numbered steps and a checklist.
- Use bullet points for clarity and keep the tone professional and instructive.
- Aim for a comprehensive yet concise response, around 300-400 words.
Guardrails
- Do not invent specific test results or bugs; focus on the plan.
- If you are unsure about a browser's behavior, state assumptions and suggest verification.
- Stay within the scope of cross-browser testing; do not delve into unrelated topics.
Example
- {{project_name}}: E-commerce site, {{browsers}}: Chrome, Firefox, Safari, {{features}}: checkout process, product search.
Follow-up prompts
- What tools can automate this testing process?
- How can I ensure performance metrics are consistent across browsers?
- What common issues should I look for during testing?