Bug 1495 - test.py claims test passed when no test was run
authorMitch Watrous <watrous@u.washington.edu>
Tue, 11 Sep 2012 13:23:53 -0700
changeset 9073 24a5b2e6f691
parent 9072 7bfaded450be
child 9074 52d752ab185d
Bug 1495 - test.py claims test passed when no test was run
doc/manual/source/test-framework.rst
test.py
--- a/doc/manual/source/test-framework.rst	Mon Sep 10 17:15:07 2012 -0700
+++ b/doc/manual/source/test-framework.rst	Tue Sep 11 13:23:53 2012 -0700
@@ -462,9 +462,6 @@
 Performance tests are those which exercise a particular part of the system
 and determine if the tests have executed to completion in a reasonable time.
 
-As of ns-3.15, there are no performance tests that are formally part of
-the test framework (contributed tests would be helpful here).
-
 Running Tests
 *************
 
--- a/test.py	Mon Sep 10 17:15:07 2012 -0700
+++ b/test.py	Tue Sep 11 13:23:53 2012 -0700
@@ -1185,7 +1185,7 @@
         # See if this is a valid test suite.
         path_cmd = os.path.join("utils", test_runner_name + " --print-test-name-list")
         (rc, suites, standard_err, et) = run_job_synchronously(path_cmd, os.getcwd(), False, False)
-        if options.suite in suites:
+        if options.suite in suites.split('\n'):
             suites = options.suite + "\n"
         else:
             print >> sys.stderr, 'The test suite was not run because an unknown test suite name was requested.'