Bugzilla – Bug 1495
test.py claims test passed when no test was run
Last modified: 2012-09-11 16:27:24 UTC
'tcp' is a real test suite, used here as an example. $ test.py --suite=tcp runs the test, as expected. However, using part of the test name: $ test.py --suite=tc reports 1 of 1 tests passed, even though $ test-runner --test-name=tc runs no tests. Details: $ ./test.py -vns tc ... Launch utils/ns3-dev-test-runner-debug --test-name=tc --stop-on-failure Synchronously execute build/utils/ns3-dev-test-runner-debug --test-name=tc --stop-on-failure --xml --tempdir=testpy-output/2012-08-24-22-26-52-CUT --out=testpy-output/2012-08-24-22-26-52-CUT/tc.xml ... PASS: TestSuite tc 1 of 1 tests passed (1 passed, 0 skipped, 0 failed, 0 crashed, 0 valgrind errors) But test-runner does this: $ ./waf --run "test-runner --test-name=tc --verbose --stop-on-failure --xml" Waf: Entering directory `build' Waf: Leaving directory `build' 'build' finished successfully (2.517s) Note that no test were done.
Bug fixed. ns-3-dev changeset: 24a5b2e6f691