Difference between revisions of "Test Triage and Intermittent Test techniques"
From CitconWiki
Jump to navigationJump to search (Created page with "Attendance * Tyler @macetw * Emil * @RobPark ==Test Triage Techniques== Often tests appear without clear reason, many commits into a single build. Unreliable machines or fram...") |
|||
| Line 6: | Line 6: | ||
==Test Triage Techniques== | ==Test Triage Techniques== | ||
Often tests appear without clear reason, many commits into a single build. Unreliable machines or frameworks, how do we respond? | Often tests appear without clear reason, many commits into a single build. Unreliable machines or frameworks, how do we respond? | ||
| + | |||
| + | Problems: | ||
| + | * Not enough information in the log | ||
| + | |||
| + | Smoke test: | ||
| + | * Impose a time limit on a smoke test | ||
| + | |||
| + | 1 team might be dedicated to triaging | ||
| + | * Build sheriff | ||
| + | * Assign person responsible | ||
| + | * File ticket | ||
| + | |||
| + | Assumed: Does everyone care that a build is red? Is a build/test cycle easy enough to reproduce? | ||
Revision as of 07:39, 24 August 2013
Attendance
- Tyler @macetw
- Emil
- @RobPark
Test Triage Techniques
Often tests appear without clear reason, many commits into a single build. Unreliable machines or frameworks, how do we respond?
Problems:
- Not enough information in the log
Smoke test:
- Impose a time limit on a smoke test
1 team might be dedicated to triaging
- Build sheriff
- Assign person responsible
- File ticket
Assumed: Does everyone care that a build is red? Is a build/test cycle easy enough to reproduce?
