terrazul-ai End-to-End Testing Skill
Tests complete user journeys through the application, validating that all components (frontend, backend, integrations) work together correctly.
When to Use
- Testing complete user flows
- Validating feature integration
- Pre-release verification
- User journey validation
- Cross-component testing
- Acceptance testing
Capabilities
- Journey mapping - Define complete user paths from start to goal
- Multi-step execution - Execute complex flows sequentially
- State validation - Verify data across frontend and backend
- Error flow testing - Test failure modes and recovery
- Performance tracking - Measure journey timing
E2E vs Other Testing
| Type | Scope | When |
|---|---|---|
| Unit | Single function | During development |
| Integration | Component interactions | After integration |
| E2E | Complete journeys | Before release |
| Regression | Existing functionality | After changes |
Workflow
Phase 1: Journey Mapping
Define the user journey:
- User goal - What the user wants to accomplish
- Starting point - Where the journey begins
- Steps - Actions to reach the goal
- Success criteria - How to know it worked
- Failure modes - What could go wrong
Phase 2: Test Preparation
Set up for execution:
- Create test accounts if needed
- Prepare test data
- Clear previous state
- Configure environment
- Document prerequisites
Phase 3: Step-by-Step Execution
For each step in the journey:
- Screenshot before action
- Perform the action (click, type, navigate)
- Wait for response
- Verify expected result
- Screenshot after action
- Log any issues
Phase 4: State Validation
Verify data consistency:
- Frontend shows correct data
- API responses match UI
- Database reflects changes
- No orphaned data
Phase 5: Reporting
Document journey results:
- Steps completed vs failed
- Issues found with severity
- Performance metrics
- Evidence (screenshots, logs)
- Overall pass/fail
E2E Test Structure
## E2E Test: [Journey Name]
**Goal**: [What user accomplishes]
**User**: [Persona/role]
**Duration**: [Expected time]
### Prerequisites
- [ ] Test account ready
- [ ] Test data available
- [ ] Environment configured
### Journey Steps
| Step | Action | Expected Result | Status |
|------|--------|-----------------|--------|
| 1 | Navigate to homepage | Page loads | |
| 2 | Click sign up | Form appears | |
| 3 | Fill form and submit | Success message | |
| 4 | Check email | Verification link | |
| 5 | Click verification | Account active | |
### Success Criteria
- [ ] User can complete full journey
- [ ] Data persisted correctly
- [ ] No errors in console
- [ ] Performance acceptable
Common E2E Journeys
New User Onboarding
Use the e2e-test skill to test the complete new user signup journey from homepage to first dashboard view
Steps:
- Visit homepage
- Click sign up CTA
- Fill registration form
- Submit registration
- Verify email (if required)
- Complete profile setup
- View dashboard
- Verify account in database
Purchase Flow (E-commerce)
Use the e2e-test skill to test the complete purchase flow from product browsing to order confirmation
Steps:
- Browse product catalog
- Search for product
- View product details
- Add to cart
- View cart
- Proceed to checkout
- Enter shipping info
- Enter payment info
- Review and confirm
- Verify order confirmation
- Check order in database
User Profile Management
Use the e2e-test skill to test updating user profile from login to confirmation
Steps:
- Log in to account
- Navigate to settings
- Update profile fields
- Save changes
- Verify success message
- Refresh page
- Verify changes persisted
- Check database updated
Data Management CRUD
Use the e2e-test skill to test creating, reading, updating, and deleting a resource
Steps:
- Log in
- Navigate to resource list
- Create new resource
- Verify in list
- View resource details
- Edit resource
- Verify changes saved
- Delete resource
- Verify removed from list
- Verify database state
Error Flow Testing
Test how the system handles failures:
Network Errors
- What happens when API fails?
- Are error messages helpful?
- Can user recover?
Validation Errors
- Are errors shown clearly?
- Can user correct and retry?
- Is form state preserved?
Session Expiry
- What happens when session times out?
- Is user redirected appropriately?
- Is data preserved?
Usage Examples
Full Journey Test
Use the e2e-test skill to test the complete signup-to-first-purchase journey
Critical Path Validation
Use the e2e-test skill to validate the login to dashboard to logout flow
Error Handling Test
Use the e2e-test skill to test payment failure handling in the checkout flow
Multi-User Flow
Use the e2e-test skill to test the admin approval workflow for new user registration
Best Practices
- Isolate tests - Each E2E test should be independent
- Use realistic data - Test with production-like data
- Test failures - Include error scenarios
- Measure timing - Track journey duration
- Clean up - Remove test data after execution
- Document dependencies - Note what must work for journey to succeed
- Screenshot everything - Visual evidence for each step
- Test on realistic browsers - Match production environment
E2E Report Format
# E2E Test Report: [Journey Name]
**Date**: [Date]
**Duration**: [Time]
**Status**: PASS / FAIL
## Journey: [Description]
### Steps Executed
| Step | Action | Result | Time | Evidence |
|------|--------|--------|------|----------|
| 1 | [Action] | PASS/FAIL | Xs | screenshot-1.png |
| 2 | [Action] | PASS/FAIL | Xs | screenshot-2.png |
### Issues Found
[List any issues with severity]
### Performance
- Total journey time: Xs
- Slowest step: [Step] (Xs)
- API calls: X
### Recommendation
[Pass / Fail - with reasoning]