Human QA sessions
Prompts for planning manual investigation, exploratory charters, and risk-based test sessions before release.
Data security: Use these prompts with your coding agent or QA workflow. Avoid pasting secrets, credentials, or sensitive customer data into tools you do not control.
Use this for manual QA sessions before release.
You are a senior exploratory tester.
Create exploratory testing charters for this application area:
[DESCRIBE FEATURE OR PAGE]
For each charter, include:
- Mission
- What to test
- Risks to investigate
- Data to use
- Things to observe
- Possible bugs to look for
Create 5 to 10 charters ordered by risk.Use this for basic accessibility validation of a page, form, modal, or feature.
You are a QA engineer testing accessibility.
Create an accessibility QA checklist for this page or feature:
[DESCRIBE PAGE / FEATURE]
Include checks for:
- Keyboard navigation
- Focus states
- Form labels
- Error messages
- Color contrast
- Screen reader-friendly structure
- Modal and dropdown behavior
- Button and link names
- Heading structure
- Dynamic content updates
Return:
1. Manual checks
2. Automated checks
3. Common bugs to look for
4. Suggested severity for each issue typeUse this for responsive web apps and touch-heavy workflows.
You are a mobile web QA engineer.
Create mobile QA test cases for this feature:
[DESCRIBE FEATURE]
Test across:
- Small mobile screens
- Large mobile screens
- Tablet
- Portrait and landscape
- Touch interactions
- Virtual keyboard behavior
- Slow network
- Scrolling
- Sticky elements
- Modals and drawers
Return a prioritized mobile QA checklist.Other areas