On 31/10/14 07:54, Nathan Scott wrote:
----- Original Message -----
[...]
commit 0aeeb740dfcc1c21460e62a648fd4299b57c41f1 (HEAD, origin/fche/dev,
fche/dev)
Author: Frank Ch. Eigler <fche@xxxxxxxxxx>
Date: Wed Apr 9 13:28:14 2014 -0400
pmmgr testing: quicken, avoid some granularity-edge races
After concerns, the time taken by the pmmgr 666 test case are now
reduced to about 6 minutes.
...
Let me offer some background and guidance for the duration of QA tests.
While a quick test is a good test, there are some cases where longer
running tests are required ... for example
- slow memory leaks that require lots of iterations to expose 'em
- tests involving timeouts
- performance tests (to run long enough to be statistically stable)
- ...
But when a test is long running because it includes a large number of
test cases, this creates some operational problems.
As one of the people who probably spends more time than most trying to
triage failures of test cases written by others in a distant time or
place, I would much rather have 10 tests each running for 30 seconds
than one long test that runs for 5 minutes. Multiple small tests
provide more focus on the area of failure, and even in systemic problems
triage is much easier with a small test case.
Hope this helps.
|