Changes between Version 11 and Version 12 of Ticket #117


Ignore:
Timestamp:
Jun 24, 2006, 3:38:36 PM (18 years ago)
Author:
Jan Wassenberg
Comment:

I think we can forget the filtering idea. First, the self-test error messages are printed via debug output, so (currently) the test executable needs to be run from within VS for them to be seen. This makes cmdline params much less useful. Also due to cxxtest design (no capability for filtering/stopping tests in a Listener), we'd have to hack cxxtest itself and pass argv through the testroot->GUIrunner->runWorld, which isn't so nice.

Also, the tests now actually work and are fine for a quick test before committing. If they need to really be run often (e.g. a quick test after every compile), it is easy to disable lengthy tests (simply prepend their test_* method name with something else).

Anyone disagree or want to see the filtering after all?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #117 – Description

    v11 v12  
    1515 * ~~make sure all tests run successfully~~
    1616 * ~~filtering: modify(/replace/subclass) !TestRunner and change its runWorld() so that it filters by the !SuiteDescription.testName().~~
    17 
    18 I think we can forget the filtering idea. First, the self-test error messages are printed via debug output, so (currently) the test executable needs to be run from within VS for them to be seen. This makes cmdline params much less useful. Also due to cxxtest design (no capability for filtering/stopping tests in a Listener), we'd have to hack cxxtest itself and pass argv through the testroot->GUIrunner->runWorld, which isn't so nice.
    19 
    20 Also, the tests now actually work and are fine for a quick test before committing. If they need to really be run often (e.g. a quick test after every compile), it is easy to disable lengthy tests (simply prepend their test_* method name with something else).
    21 
    22 Anyone disagree or want to see the filtering after all?