This page is under construction. More content coming soon!
Running Tests
Execute individual tests or entire test suites and monitor progress in real-time.Execution Methods
- Individual Test
- Test Run
- Quick Run
Run a Single Test
Execute Steps
Follow the test steps and mark results:
- ✅ Pass: Step executed successfully
- ❌ Fail: Step failed (add failure details)
- ⏸️ Skip: Step was skipped
- 🚫 Blocked: Cannot execute due to blocker
Test Run Dashboard
Monitor your test run with real-time metrics:Progress
Overall completion percentage and status breakdown
Execution Status
See which tests are running, passed, failed, or blocked
Team Activity
Track who is executing which tests
Recording Results
Marking Steps
Marking Steps
As you execute each step:
- Click Pass if the actual result matches expected
- Click Fail if results don’t match (add screenshot/notes)
- Click Skip if step couldn’t be tested
- Click Blocked if blocked by another issue
Adding Evidence
Adding Evidence
Attach supporting evidence:
- Screenshots: Capture what you see
- Logs: Paste relevant error logs
- Videos: Record complex issues
- Files: Attach test data or outputs
Defect Linking
Defect Linking
Link test failures to defects:
- Click “Create Bug” from failed test
- Or link to existing bug tracker issue (JIRA, GitHub, etc.)
Notes & Comments
Notes & Comments
Add context for future reference:
- Observed behavior
- Environment specifics
- Workarounds tried
- Next steps
Test Run Configuration
- Environment
- Build
- Schedule
- Notifications
Select where tests will run:
- Development: Local testing
- Staging: Pre-production validation
- Production: Smoke tests in prod
Best Practices
Clear Test Runs
Name runs descriptively: “Sprint 24 Regression” not “Test Run 42”
Document Failures
Always add screenshots and logs for failures
Link Defects
Connect failures to bug tracker for traceability
Regular Smoke Tests
Run smoke tests after every deployment