Run Tests
Running tests is where you verify that all criterion have been met. Test execution creates a documented record of validation activities and results.
Quick Steps
- Navigate to your versioned Statement of Work
- Go to the Tests tab
- For each test:
- Click Execute Test
- Follow test functions step-by-step
- Record actual results
- Mark each function as Pass/Fail
- Add evidence (screenshots, logs, etc.)
- Submit the test run
Test Execution Process
1. Preparation
- Ensure test environment is ready
- Gather any required test data
- Review test setup requirements
- Have evidence capture tools ready
2. Execution
- Follow each test function precisely
- Document what you observe
- Capture evidence as you go
- Note any deviations or issues
3. Documentation
- Record actual results for each function
- Attach relevant evidence files
- Add notes for clarification
- Mark overall test status
Recording Results
For each test function:
- Expected Result: Pre-defined in the test
- Actual Result: What you observed
- Status: Pass/Fail/Blocked
- Evidence: Screenshots, logs, data exports
- Notes: Additional context or observations
Evidence Types
Screenshots
- UI states and outputs
- Error messages
- Confirmation screens
- Data displays
Logs
- System logs
- Application logs
- API responses
- Database queries
Documents
- Export files
- Reports
- Configuration files
- Test data sets
Test Run States
In Progress
- Test execution has started
- Some functions may be complete
- Can be paused and resumed
Completed
- All test functions executed
- Results recorded
- Ready for review
Passed
- All functions passed
- Criterion is satisfied
- Evidence supports results
Failed
- One or more functions failed
- Criterion not satisfied
- Issues documented
Blocked
- Test cannot be completed
- External dependency issue
- Requires resolution
Bulk Testing
For efficiency, you can:
- Test Suites: Group related tests
- Batch Execution: Run multiple tests together
- Parallel Testing: Multiple testers work simultaneously
- Test Templates: Reuse common test patterns
Best Practices
- Follow Instructions Exactly: Don't deviate from test functions
- Document Everything: Even unexpected behaviors
- Capture Evidence: More is better than less
- Be Objective: Report what you see, not what you expect
- Test Promptly: Run tests soon after version creation
- Collaborate: Discuss blockers or ambiguities immediately
What's Next?
After running all tests, proceed to analyze and iterate based on the results.