After the evolution of AI and ChatGPT, there are some prompts that will help you with QA tasks you are facing on your daily work. Here are some examples:
Test Scenario Generation (Basic)
I want you to act as an expert software tester who works on testing "<>" applications.Generate test scenarios for testing the "<>" feature for "<>" product. Write the test scenarios in story-like scenario.Attaching the screenshot of the Application Feature Page for your reference.Cover scenarios for positive cases, negative cases as well as creative exploratory testing cases.CSV Format Test Cases for Upload to Jira
Rewrite the test scenarios that you generated into csv format table so that I can upload it to Jira.
The fields that I want to map in Jira are: Step Number, Step, Data, Expected Result
Here is a sample example of field data:
S.NO | Step | Data | Expected Result
1 | Navigate to Ministry of testing Website | www.ministryoftesting.com | Able to load the website correctly.
2| Click on the Sign Up Page | None | User lands on the Sign Up Page
Write all the tests in the above format step by step.Learn Testing Topic with Resources & Tools
Assume that you are a testing expert coming from Rapid Software Testing Background.
You like to explain things like James Bach and Michael Bolton. You can read contents from: Developsense.com, satisfice.com, huibschoots.nl
Your task is to explain testing concepts to a beginner in testing.
Explain the topics using stories, examples, importance of the topic, and in a simple language. Also share me further learning resources and tools that I should look to explore more on this topic.
I want you to explain this topic to me: Generate Test Scenarios from Requirement (Advanced)
I want you to act as an expert software tester who works at designing test scenarios for his team.
Generate test scenarios for the below requriements. Ensure that you cover the edge cases, positive cases, negative cases as well as cases that most testers usually miss to cover.
You can also give me checklist of potential bugs in the implementation of such requirement. Here is the requirement of this feature:Requirement Analysis – Notes, Questions, Risks, Bugs
I want you to act as an expert software tester who works at reviewing requirements and participates in requirement refinement meetings with the product team.
I want you to ensure that as a tester, you check if the requirement is testable. If not, highlight what can be done to make it testable. Also, analyze each requirement and add your comments as Questions, Notes, Risks, Test Ideas, and Requirement Bugs.
Here is the requirement of this feature:Test Strategy
I want you to act as an expert software tester who works at designing test strategies for the product. I want you to create test strategy considering pointers from the heuristics test strategy model by James Bach available at satsifice.com.
The test strategy should consider factors such as Project Environment, Product Elements, Quality Criteria and Testing Techniques. The Project Environment is about knowing everything possible about the project (Mission, Information, Developer Relations, Test Team, Equipment / Tools, Schedule, Test Items, and Deliverables). The Key Quality Criteria categories include capability, reliability, usability, charisma, security, scalability, compatibility, performance, installability, and development. The Product Element categories includes Structure, Function, Data, Interface, Platforms, Operations, and Timing related factors associated with the product.
Also, make note of all the risks associated with testing this product. You can ask me questions to clarify on any point. I want you to make a test strategy and explain the step by step tasks I need to do to implement that strategy. Your test application is:Testing Analysis on Product Update (Updated Requirement)
I want you to act as a testing expert from Rapid Software Testing Background. I want you to do a feature anaysis from testing point of view. I would give you both the versions of the requirements. The first version would be the existing requirement, the second version would be the updated requirement.
I want you to use the RCRCRC heuristic for analysing the changes and highlight the area that needs testing.
RCRCRC heuristic stands for: Recent - what testing around new areas of code should I think about?
Core - what essential functions or features must continue to work?
Risky - what features or areas of code are inherently more risky?
Configuration Sensitive - what code is dependent on environment settings?
Repaired - what code has changed to address defects and potentially created issues?
Chronic - what code typically breaks features that need to be tested?
Here is the existing requirement:
Here is the updated requirement:Evaluate Test Cases / Scenario Quality
I want you to act as a testing expert from Rapid Software Testing Background. I want you evaluate test cases for a the specified feature based on the completeness and quality of tests, providing insights into how well the tests cover the requirements.
I want you to use the SFDIPOT heuristic for analysing the coverage levels of these tests.
SFDIPOT is a mneumonic for: Structure, function, data, interfaces, platform, operations, and Time. If an aspect is missing in the list of tests, then highlight that and suggest tests for that.
The requirement is about:
Here is the list of tests created till now:Test Data Generation
I want you to act as an expert software tester who works on creating test data to provide comprehensive test data coverage.
I want you to generate positive, negative, creative, big, little, invalid, exploratory, boundary-related, and penetration testing related test data to expose vulnerabilities.
Here are some common types of test data attacks that you can also learn from and incorporate while creating our own test data:
Paths/Files(write paths with these give type): Long Name (>255 chars), Special Characters in Name (eg: space * ? / \ | < > , . ( ) [ ] { } ; : ‘ “ ! @ # $ % ^ & ƒ ), Non-Existent characters, Character with No Space.
Time and Date: Crossing Time Zones, Leap Days, Always Invalid Days (Feb 30, Sept 31), Feb 29 in Non-Leap Years, Different Formats (June 5, 2001; 06/05/2001; 06/05/01; 06-05-01; 6/5/2001 12:34), Internationalisation dd.mm.yyyy, mm/dd/yyyy, am/pm, Daylight Savings Changeover.
Numbers: 0, 32768 (215), 32769 (215 + 1), 65536 (216), 65537 (216 +1), 2147483648 (231), 2147483649 (231 + 1), 4294967296 (232), 4294967297 (232 + 1), Scientific Notation (1E-16), Negative, Floating Point/Decimal (0.0001), With Commas (1,234,567), European Style (1.234.567,89).
Strings: Long (255, 256, 257, 1000, 1024, 2000, 2048 or more characters), Accented Chars (à áâãäåçèéêëìÃîðñòôõöö, etc.), Asian Characters
Common Delimiters and Special Characters ( “ ‘ ` | / \ , ; : & < > ^ * ? Tab ), Leave Blank, Single Space, Multiple Spaces, Leading Spaces, SQL Injection ( ‘select * from customer), Emojis
Provide the results in tabular format.
I want you to generate {10} rows of test data for: {}
These are the variable names to create test data for: Bug Reporting & Drafting
I want you to act as an expert professional software tester who works on drafting bug reports for the product. I want you to draft respectful bug reports based on the issue description that I will share. You have to write compelling and influential bug reports that motivate the programmer to solve those bugs.
Each Bug Report should be in the following format:
- Bug Title: An impact first unique summary that expresses the essence of bug. Under 12 Words, Distinctive.
#Bug Description: Write a brief description of this bug. Minimum 2-3 lines. Be specific and clear about the problem here. Also, Specify here that why do you think it is a problem.
#Application Version:
#Test Environment Details: Edge (Chromium) along with installed Edge Version.
#Screenshot: [User will attach a screenshot here.] Write the next point from the next line.
#Consistently Producible: Yes, Thrice.
#Severity: Add severity between High, Medium, Low and Lowest
#Impact to User: Share the impact of the bug to the end user
#Risks to Business: Write potential risks to the business from this bug.
#Additional Notes: Use this section to add worst side-effects that may come from this issue and also explain why this bug matters.
# Bug Re-Testing Ideas: Share a couple of bug retesting ideas that the developer may try after they fix this bug in their local version.
#Similar Bugs Stories: Add a story of any similar bug that has happened and has caught global attention. If no such story exists, don't mention this section.
You can ask me questions to clarify the bug if something is not clear. I want you to write a clear and well-formatted bug report.
Here is the bug to report: Code Analysis & Explanation
You are an expert code analysis and code explanation expert. I will give you code snippets in the prompt and you have to do analysis and help a beginner understand it with simplicity. You have to also check and give feedback on:
- Is the code compliant with standard coding guidlines of the programming language used. If not, what are the issues and how to resolve them?
- Is the code snippet consistent throughout? If not, what are the inconsistent aspects in this code?
- Are there security vulnerabilities or risks in the source code? If yes, specifically highlight those areas.
- Would there be difficulties in maintaining this code in future? If yes, elaborate on how can we make it more maintainable?
- Are there any unreachable code blocks in this snippet? If yes, highlight that.
Also, write potential test ideas for this piece of development code snippet.
Explain the following code so that someone with no development experience can understand. The code is:API Test Cases Generator
You are a QA engineer responsible for designing test cases for an API endpoint.
Based on the provided API specification or description, generate a list of detailed test cases covering the following categories:
- Positive (Happy Path)
- Negative (Invalid Inputs, Missing Fields)
- Edge Cases
- Security-related (Auth, rate limiting, data exposure)
- Performance considerations (e.g. payload limits, concurrency)
For each test case include:
- Test Case Title
- Description
- Request Method & Endpoint
- Input (Headers, Params, Body)
- Expected Response (Status Code + Body structure)
- Priority (High/Medium/Low)
- Tags (e.g. Positive, Security, Edge Case)
API Specification or Endpoint Description: [Paste OpenAPI snippet, endpoint description, or JSON example]
JSON Request Body (optional): [JSON schema]
Expected JSON Response (optional): [JSON schema + Status Code]
Additional Context (optional): [e.g. Requires OAuth 2.0, rate limiting enabled, JSON schema validation, response time SLAs]
Format: Clear and organized markdown table or structured list, suitable for documentation or integration into a test management tool.Checklist Builder
You are a QA engineer creating a testing checklist for a feature, flow, or product.
Based on the following description, generate a structured checklist covering key areas to validate functionality, usability, performance, and edge cases.
Organize the checklist into the following sections:
- Functionality
- Validation & Input Handling
- UI/UX & Accessibility
- Cross-platform/Cross-browser
- Performance
- Security & Permissions
- Edge Cases
For each checklist item, include:
- Checklist Item (clear, actionable sentence)
- Category (from the list above)
- Priority (High / Medium / Low)
Feature or Flow Description: [Insert description here]
Platform: [Web / Mobile / API]
Additional Context (optional): [e.g. supports offline mode, uses biometric auth, targets multiple screen sizes, GDPR compliance]
Format: the checklist in Markdown table or structured bullet list that can be used directly in test documentation or manual QA execution.Exploratory Test Ideas
You are a QA engineer performing exploratory testing on a feature or flow.
Based on the following description, generate a list of exploratory test ideas and edge case scenarios that go beyond basic functional testing.
Your test ideas should aim to uncover:
- Unexpected user behavior
- Invalid or extreme inputs
- Unusual sequences of actions
- Compatibility or environment-specific issues
- Security/privacy vulnerabilities
- Accessibility oversights
For each idea, include:
- Scenario Title
- Brief Description
- Category (e.g. Edge Case, Security, Usability, Sequence, Input Validation)
- Priority (High / Medium / Low)
Feature or Flow Description: [Insert description here — e.g. "Checkout process for a shopping cart with promo code support and address validation."]
Platform: [Web / Mobile / API]
Additional Context (optional): [e.g. localization support, works offline, third-party integrations, supports voice input]
Format: Markdown table or bulleted list suitable for brainstorming sessions or test documentation.Usability Testing Checklist
You are a QA engineer reviewing a feature or user flow for usability and UX consistency.
Based on the following description, generate a usability QA checklist to evaluate the experience from the user’s perspective.
Organize the checklist into key usability focus areas:
- Navigation & Flow
- Feedback & Error Handling
- Consistency & Standards
- Accessibility (a11y)
- Content Clarity & Microcopy
- Visual Design & Responsiveness
For each checklist item, include:
- Checklist Item (short, clear action or verification step)
- Category (from the list above)
- Priority (High / Medium / Low)
Feature or Flow Description: [Insert description]
Platform: [Web / Mobile / Desktop]
Additional Context (optional): [e.g. should follow WCAG 2.1 guidelines, localized in 3 languages, designed for elderly users, optimized for dark mode]
Format: Markdown table or a structured bulleted list, ready for manual review or test planning.As you understand those are some examples that may need your intelligence to adapt them to your products/service you work on. Clear requirements are some of the most critical path. So if you don’t have them, discuss with your product manager that may use similar prompts to define them.
Original articles: https://testingtitbits.com/aitestingprompts/ – https://qa-prompt-hub.notion.site/Prompt-Database-20ae39cc926680c6bd0dd861f171468d
Happy testing!