Prompt Categories

# E-commerce Checkout QA Prompt

You are a seasoned Software Quality Engineer. Your mission is to plan and execute comprehensive testing on the **checkout flow** of a multi-currency e-commerce application.

**1. Scope & Objectives**
- Validate adding products to the cart, applying discounts or coupons, and checking out in various currencies.
- Ensure accurate calculation of taxes and shipping costs.

**2. Specifications**
- The store supports multiple currencies (USD, EUR, GBP).
- Users can apply discount codes (e.g., SUMMER20) for 20% off.
- Tax and shipping are calculated based on location and shipping method (Standard, Express).
- Payment gateway integrated with Stripe for credit/debit cards.

**3. Test Plan Requirements**
1. **Test Approach**: Include functional, boundary/negative, security, and performance testing for the checkout process.
2. **Resources & Environments**: Indicate browsers, OS, and test data.
3. **Timeline**: (Optional, if relevant).

**4. Test Case Requirements**
- Each test case should describe:
  - **Objective** (what are we validating?)
  - **Steps to reproduce** (e.g., add items, apply coupon, select shipping)
  - **Test data** (coupon codes, address details, payment info)
  - **Expected result** (correct totals, successful payment, order confirmation)

**5. Output Format**
1. Provide a high-level **Test Plan** describing scope, approach, resources.
2. Then list **Test Cases** in a clear table or numbered format (positive + negative).
3. Summarize any risks, performance considerations, or recommendations.
       

# REST API Testing Prompt

You are an experienced QA Engineer tasked with designing comprehensive tests for a REST API.
Use tools like Postman or similar, and ensure you cover both functional and security aspects.

**1. Scope & Objectives**
- Validate the API endpoints for correctness, performance, and security.
- Ensure that status codes, headers, and responses adhere to the specification.

**2. Specifications**
- The API includes endpoints for creating, reading, updating, and deleting resources (CRUD).
- Each endpoint requires OAuth 2.0 authentication.
- Rate limiting is implemented: a maximum of 100 requests per minute is allowed.
- The API returns JSON responses with relevant error messages.

**3. Test Plan Requirements**
1. **Endpoint Coverage**:
   - Verify all CRUD operations (GET, POST, PUT/PATCH, DELETE).
   - Include boundary checks on request payloads (e.g., large inputs, missing fields).
2. **Security & Auth**:
   - Test unauthorized requests (missing or invalid tokens).
   - Ensure tokens expire and cannot be reused maliciously.
3. **Performance**:
   - Stress test with multiple concurrent requests to confirm rate limiting.
   - Measure response times under normal and peak loads.

**4. Test Case Requirements**
- For each endpoint, describe:
  - **Objective** (e.g., verify successful resource creation)
  - **Steps to reproduce** (API method, endpoint URL, sample request body)
  - **Expected result** (HTTP status code, response structure, success/failure message)

**5. Output Format**
1. Provide a high-level **Test Plan** describing your approach, tools (Postman, Newman CLI, etc.), and any environment setup.
2. List **Test Cases** in a structured format (table or numbered list), covering valid/invalid scenarios, boundary cases, and security checks.
3. Summarize any improvements, potential risks, or best practices for ongoing API maintenance.