Mastering Prompt Engineering for Automation Testers

// Weak Context
"You are a helpful assistant."

// Strong Context for Automation
"You are a Senior SDET with 8+ years of experience in Python automation. 
You specialize in Selenium WebDriver, pytest, and API testing with requests.
You follow PEP8 strictly and believe in clean, maintainable code.
You have worked extensively with e-commerce and banking applications."

// Vague Task
"Write a login test."

// Precise Task
"Write a pytest function 'test_login_with_valid_credentials' that:
1. Navigates to /login
2. Enters username 'standard_user' and password 'secret_sauce'
3. Clicks the login button
4. Asserts that the URL contains '/inventory' after login
5. Asserts that the shopping cart icon is visible"

// Constraints for a Selenium Script
"CONSTRAINTS:
- Use WebDriverWait with explicit waits. NEVER use time.sleep() or implicit waits.
- Use CSS selectors as the primary locator strategy. XPath only as fallback.
- All locators must be defined as class constants at the top of the Page Object.
- Do not catch generic exceptions. Handle specific Selenium exceptions.
- All methods must have type hints and docstrings.
- Use the By class from selenium.webdriver.common.by, not string literals."

// Output Specification Examples

// For Code Generation
"OUTPUT: Provide only the Python code. No explanations before or after. 
Include inline comments for complex logic only."

// For Test Case Documentation  
"OUTPUT: Return a markdown table with columns: 
Test ID | Test Name | Preconditions | Steps | Expected Result | Priority"

// For Debugging
"OUTPUT: Return a JSON object with keys: 
'root_cause', 'affected_components', 'fix_suggestion', 'confidence_score'"

"Before writing the code, think through:
1. What is the user flow being tested?
2. What elements need to be interacted with and in what order?
3. What could go wrong (exceptions to handle)?
4. What assertions prove the test passed?

Then provide the implementation."

Generate a CheckoutPage following this structure.
Use the supplied application selectors; identify any missing ones.

class LoginPage:
    USERNAME = (By.CSS_SELECTOR, "[data-test='username']")

    def __init__(self, driver):
        self.driver = driver
        self.wait = WebDriverWait(driver, 10)

    def enter_username(self, value):
        field = self.wait.until(EC.visibility_of_element_located(self.USERNAME))
        field.clear()
        field.send_keys(value)

Include imports, driver fixture requirements, and an assertion
that proves the checkout action completed.

// For Test Case Discovery
"You are a QA Architect who has broken into production systems for 15 years. 
You think like a hacker. Given this login form, generate 10 edge cases 
that most testers would miss. Focus on security, input validation, 
and race conditions."

// For Code Review
"You are a tech lead reviewing a junior engineer's Selenium code.
Be constructive but thorough. Identify issues in: reliability, 
maintainability, performance, and adherence to best practices. 
Rate severity as Critical/Major/Minor."

// Round 1: Generate Structure
"Design the class structure for a Page Object pattern for an e-commerce site. 
Just the class names and method signatures, no implementation yet."

// Round 2: Implement Core
"Now implement the ProductPage class with full locators and methods."

// Round 3: Add Edge Cases  
"Add error handling for the case where a product is out of stock 
and the Add to Cart button is disabled."

Give me XPath for the login button.

"Given this HTML snippet:
<button class='btn btn-primary submit' id='login-btn-7829' data-testid='login-submit'>
<span>Sign In</span>
</button>

Generate 3 locator strategies in order of reliability:
1. CSS Selector (preferred)
2. XPath (as backup)  
3. Fallback strategy

CONSTRAINTS:
- Avoid dynamic IDs (like 'login-btn-7829')
- Prefer data-testid attributes
- XPath must be relative, not absolute
- Explain why each locator is resilient to UI changes"

Write a page object for the cart page.

"CONTEXT: Senior SDET writing Selenium Python Page Objects.

TASK: Generate a complete Page Object for a Shopping Cart page with:
- Cart item list (each item has: name, price, quantity, remove button)
- Total price display
- Checkout button
- Continue Shopping link

CONSTRAINTS:
- Use @property decorators for element access
- All waits must be explicit using WebDriverWait
- Include a method to get cart item count
- Include a method to remove item by name
- Include a method to verify total price calculation
- Follow POM best practices: no assertions in Page Object, return self for chaining
- Type hints on all methods

OUTPUT: Python code only. Comments on non-obvious logic."

Write test cases for the search feature.

"CONTEXT: E-commerce website with search functionality that supports:
- Text search
- Category filters
- Price range filters
- Sort by (relevance, price, rating)

TASK: Generate a comprehensive test case matrix covering:
1. Positive scenarios (valid searches)
2. Negative scenarios (empty/invalid inputs)
3. Boundary conditions (min/max values)
4. Edge cases (special characters, SQL injection attempts, XSS payloads)
5. Performance scenarios (response time limits)

OUTPUT: Markdown table with columns:
| TC_ID | Category | Scenario | Input | Expected Result | Priority |

Generate at least 15 test cases across all categories."

Generate some test data for registration.

"CONTEXT: User registration form for a German e-commerce platform.

TASK: Generate 10 user profiles for registration testing.

INCLUDE:
- 3 valid users with realistic German names and addresses
- 2 users with edge case emails (long email, subdomain, plus addressing)
- 2 users designed to fail validation (XSS in name, SQL injection in email)
- 2 users with Unicode characters in names (umlauts, accents)
- 1 user with minimum valid data (only required fields)

OUTPUT: JSON array. Each object must have:
first_name, last_name, email, password, street, city, postal_code, country, phone

Mark each with a 'test_category' field: 'valid', 'edge_case', 'security', 'unicode', 'minimal'"

"CONTEXT: Selenium test failed in CI. I need root cause analysis.

ERROR LOG:
selenium.common.exceptions.StaleElementReferenceException: 
Message: stale element reference: element is not attached to the page document
at test_add_to_cart (test_cart.py:47)
 
CODE SNIPPET (test_cart.py:40-50):
def test_add_to_cart(self):
products = self.driver.find_elements(By.CSS_SELECTOR, '.product-card')
for product in products:
    add_btn = product.find_element(By.CSS_SELECTOR, '.add-to-cart')
    add_btn.click()
    time.sleep(1)

TASK: Analyze this failure and provide:
1. Root cause explanation
2. Why this pattern causes StaleElementReference
3. Corrected code that handles dynamic DOM updates
4. Preventive pattern to avoid this in future tests

Be specific to Selenium WebDriver internals."

"CONTEXT: Testing a REST API with pytest and requests library.

API ENDPOINT: POST /api/v1/orders
REQUEST BODY: {
"user_id": "string",
"items": [{"product_id": "string", "quantity": int}],
"shipping_address": {...},
"payment_method": "credit_card" | "paypal"
}

TASK: Generate a comprehensive pytest test module that covers:
1. Happy path with valid order
2. Invalid user_id (404 expected)
3. Empty items array (400 expected)
4. Quantity = 0 and negative quantity
5. Invalid payment_method
6. Schema validation of response
7. Response time assertion (< 500ms)

CONSTRAINTS:
- Use pytest fixtures for API client setup
- Use pytest.mark.parametrize for data-driven tests
- Include both status code and response body assertions
- Use pydantic or jsonschema for response validation

OUTPUT: Complete pytest module, production-ready."

"CONTEXT: Appium Python test for Android app, using pytest.

TASK: Generate a test that:
1. Launches the app
2. Handles the onboarding flow (3 swipeable screens with Skip button)
3. Logs in with test credentials
4. Navigates to Profile and verifies user name is displayed

CONSTRAINTS:
- State the installed Appium server, driver, and Python-client versions; use W3C capabilities
- Handle permissions popup if it appears (location, notifications)
- Use W3C pointer actions or a documented driver-specific mobile gesture
- Implement explicit waits with Selenium WebDriverWait
- Make it resilient to slow emulator startup

OUTPUT: Complete pytest test file with fixture for driver setup/teardown."

// DON'T
"Write Selenium test."

// WHY IT FAILS
- What language? What framework?
- What is being tested?
- What page structure?
- What assertions matter?

// DON'T
"Here's my entire 500-line page object, my conftest.py, my pytest.ini, 
three other page objects, and the full HTML of the page. 
Fix the flaky test."

// WHY IT FAILS
- Exceeds context window / drowns the signal
- AI can't identify what's relevant
- Solution: Extract ONLY the relevant snippet

// DON'T
"Generate test data for user registration."

// WHAT YOU GET
- Hardcoded values that match nothing
- Fake data that fails validation
- No edge cases
- Wrong format (JSON vs CSV vs Python dict)

// ALWAYS SPECIFY constraints and output format

// DON'T
"Give me a complete automation framework with page objects, 
API clients, database utilities, reporting, parallel execution, 
Docker setup, and CI/CD pipeline."

// WHY IT FAILS
- Too many interconnected decisions
- Output will be superficial on everything
- Solution: Break into 10+ focused prompts