Tips

Test organization

Working Set Management

• Group related pages together
• Keep working sets focused on specific features
• Clear working set between different testing areas

Test structure

• Use descriptive test names
• Follow the Arrange-Act-Assert pattern
• Keep tests independent and atomic

Writing effective prompts

Be specific

✅ Good:

/test Verify login form validation:
1. Enter invalid email format
2. Check for "Invalid email" message
3. Enter valid email but wrong password
4. Check for "Invalid credentials" message

❌ Bad:

/test Check if login works

Include verification steps

✅ Good:

/test Add item to cart and verify:
- Cart icon shows correct count
- Item appears in cart sidebar
- Total price is updated

❌ Bad:

/test Add item to cart

Test maintenance

Regular updates

• Review and update tests when UI changes
• Keep working sets current
• Update API keys before expiration

Error handling

• Include error scenarios in tests
• Verify error messages and states
• Handle loading states and transitions

Performance considerations

Working Set Size

• Keep working sets manageable (3-5 pages max)
• Split large flows into smaller working sets
• Clear unused pages regularly

Model selection

• Use faster models for simple tests
• Reserve GPT-4o for complex scenarios
• Balance speed vs. capability needs

Collaboration

Documentation

• Add comments to complex tests
• Document custom commands
• Share working sets with team members

Version control

• Store tests in version control
• Use consistent naming conventions
• Include setup instructions