Functional tests take a long time

From CitconWiki
Revision as of 16:20, 6 April 2008 by MarkEWaite (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...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

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
Retrieved from "http://citconf.com/wiki/index.php?title=Functional_tests_take_a_long_time&oldid=5677"