[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lmi] Problem of the week: testing a testing tool
From: |
Greg Chicares |
Subject: |
[lmi] Problem of the week: testing a testing tool |
Date: |
Sun, 24 Dec 2006 12:19:54 +0000 |
User-agent: |
Thunderbird 1.5.0.4 (Windows/20060516) |
make unit_tests build_type=mpatrol unit_test_targets=input_test
[add '.exe' at the end for msw]
Running input_test:
Speed tests...
Overhead: [3.931e+000] 1 iteration took 3930 milliseconds
Vector : [9.064e+000] 1 iteration took 9063 milliseconds
Read : [1.#IOe+000] 0 iterations took 15031 milliseconds
Write : [7.772e+000] 1 iteration took 7771 milliseconds
'cns' io: [1.#IOe+000] 0 iterations took 54502 milliseconds
'ill' io: [1.#IOe+000] 0 iterations took 14409 milliseconds
.... 27 tests succeeded
no errors detected
mpatrol: total warnings: 0
mpatrol: total errors: 0
0. What's obviously wrong here on the face of it?
1. Which revisions introduced defects observable above?
2. How could those defects have been detected automatically?
3. How could those defects have been prevented?
4. How should those defects be removed?
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [lmi] Problem of the week: testing a testing tool,
Greg Chicares <=