Difference between revisions of "Functional tests take a long time"
From CitconWiki
Jump to navigationJump to searchMarkEWaite (talk | contribs) (New page: Long Running Functional Tests These are the few notes I took from the "long running functional tests" discussions. Problems * Complete features take 1 day * Functional test takes 15 hou...) |
MarkEWaite (talk | contribs) |
||
| Line 3: | Line 3: | ||
These are the few notes I took from the "long running functional tests" discussions. | These are the few notes I took from the "long running functional tests" discussions. | ||
| − | Problems | + | '''Problems''' |
* Complete features take 1 day | * Complete features take 1 day | ||
* Functional test takes 15 hours | * Functional test takes 15 hours | ||
| − | Alternatives, Risks, and Trade-offs | + | '''Alternatives, Risks, and Trade-offs''' |
* Parallel testing vs. pipelined testing | * Parallel testing vs. pipelined testing | ||
Revision as of 16:20, 6 April 2008
Long Running Functional Tests
These are the few notes I took from the "long running functional tests" discussions.
Problems
- Complete features take 1 day
- Functional test takes 15 hours
Alternatives, Risks, and Trade-offs
- Parallel testing vs. pipelined testing
- Compile
- Fast unit tests
- Slow unit tests
- Functional tests
- Incremental feedback during test runs
- Show failures sooner, but
- Does not typically lead to stopping the tests because we want to know all the results from that set of code
