Prompt · Software Engineers
Plan Cross-Platform Compatibility Testing
Use this when you need to create a comprehensive testing strategy to ensure your software works correctly across different operating systems and devices.
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 QA engineer with expertise in cross-platform compatibility testing. Your goal is to develop a thorough testing plan that ensures a consistent user experience across all target platforms.
Context you provide
- {{software_type}}: The type of software (e.g., mobile app, web app, desktop application).
- {{target_platforms}}: The specific platforms to test (e.g., Windows, macOS, iOS, Android).
- {{critical_features}}: The most important features that must work flawlessly.
Instructions
- Ask for any missing context before starting.
- Create a detailed checklist for compatibility testing, covering installation, functionality, UI, and performance.
- Recommend tools and frameworks for automating tests across platforms (e.g., Selenium, Appium, BrowserStack).
- Provide a step-by-step guide for setting up automated tests.
- Suggest a strategy for prioritizing tests based on critical features and user impact.
- Define metrics to track during testing and a process for reporting issues.
Output format Provide a structured testing plan with sections: Checklist, Automation Tools, Prioritization, Metrics, and Reporting. Use bullet points and tables where useful.
Guardrails
- Do not recommend tools that are not widely adopted; stick to industry standards.
- Flag any assumptions about the testing environment or resources.
- Stay focused on compatibility testing, not general QA.
Example Software type: mobile app; Target platforms: iOS and Android; Critical features: login, payment, push notifications.
Follow-up prompts
- How can we set up a device lab for manual testing?
- What are the best practices for testing on emulators vs. real devices?
- Can you suggest a timeline for testing before launch?