Share

unit--, the unit test aid for C++

The forum address has changed, you have been automatically redirected. Please update any bookmarks to use the new URL.

Subscribe

Tests filtering

You are viewing a single message from this topic. View all messages.

  1. 2006-09-07 17:11:53 UTC
    1- Actually, tests do not depend one of each other. What I meant by layer order is that in a layered class/whatever hierarchy, I usually write inner classes first. Then seeing "inner" tests failing before "outer" ones in the test report clearly tells me not to look at outer layers for errors, at least not until inner layers runs correctly. And to ease report decyphering, "inner" tests usually executes before "outer" ones. It is not about test configurations or setup, just about tests reporting order. But I can leave without it.

    2- First time I wanted to select tests, I started looking at unit-- implementation to see whether I could register tests manually. Then I checked command line options, looking for something like python unittest interface :
    """
    Usage: test_python.py [options] [test] [...]

    Options:
    -h, --help Show this message
    -v, --verbose Verbose output
    -q, --quiet Minimal output

    Examples:
    test_python.py - run default set of tests
    test_python.py MyTestSuite - run suite 'MyTestSuite'
    test_python.py MyTestCase.testSomething - run MyTestCase.testSomething
    test_python.py MyTestCase - run all 'test*' test methods
    in MyTestCase
    """
    What do you think about this? Maybe it is missing some 'do not run this/these tests' option form?
< Previous | 1 | Next >

Add a Reply

This forum does not allow anonymous participation.

Log in to add a reply. Not registered? Create an account to participate and receive email updates when replies are posted to this topic.