JUnit Test Selection Manual

     The test runner is invoked in the same way as the standard textui test runner implementation: java junit.textui.SelectiveTestRunner<testsuite> 
     However it supports the following additional options:

• -names: Lists each of the test cases encountered as a test number and test name, which can be used to select the test using the options described below. The test cases are not run. 
       java junit.textui.SelectiveTestRunner -names subject.tests.ATestSuite
• -sID<id1,id2,id4-id7,...,idN>: Select tests by number (ID). Accepts a comma-delimited list of test numbers identifying tests to be run. Ranges are allowed. 
            Invoke the test runner on a single test case and capture the output directly with redirection (such as in a javamts script)
       java junit.textui.SelectiveTestRunner -sID 5 subject.tests.ATestSuite >& t5
• -sName <name1,name2,...,nameN> Select tests by name. Accepts a comma-delimited list of test names.
       java junit.textui.SelectiveTestRunner -sName subject.tests.testMethod subject.tests.ATestSuite
• -o<dir>: Instructs the test runner to save outputs of test cases to directory 'dir'. The files will be named in the form tX where X is the test number. (For example, running tests 3-5 would produce the files 't3', 't4', and 't5').
  
            Run multiple test cases, saving results to 'outputs' directory
       java junit.textui.SelectiveTestRunner -sID 3,5,9-12 -o outputs subject.tests.ATestSuite
  
  When the '-o' option is active, the test runner prints a notification before each test case is run, in the same style as javamts scripts. Generally, it is expected that the '-o' option will be used unless only one test case is being run. Without the '-o' option, only the output of test cases is printed to the console. This allows a javamts script to invoke the test runner for individual test cases and treat the output as if it were the result of invoking the test case directly. (Note: If the '-d' option is also used, the difference message will always be printed).
• -d<dir>: Instructs the test runner to difference the output of each test case with the output from a previous run of that test case, found in directory 'dir'. A message is printed for outputs that differ. Trace files will also be diffed when executing a traced run. 
            Run multiple test cases, saving outputs, and diffing against previous outputs, in 'previous' directory. 
       java junit.textui.SelectiveTestRunner -sID 3,5,9-12 -o outputs -d previous subject.tests.ATestSuite
            (Note: It is also possible to difference against previous outputs while discarding the outputs of the current test run).
• -p: Instructs the test runner to prioritize the tests. The tests will be executed in a specified order as inserted in command line.
       java junit.textui.SelectiveTestRunner subject.tests.ATestSuite -p -sID 3,1,2
• -univ<name>: Generate a universe file that can be used to run the same set of tests one at a time.
       java junit.textui.SelectiveTestRunner subject.tests.ATestSuite -sID 1-3 -univ UniverseFile.txt
• -t <options> Instructs the test runner to collect trace information for each test case in trace files. The subject classes must be instrumented using the '-junit' option to sofya.ed.cfInstrumentor. The <options> portion is a comma delimited list of option name/value pairs in the form 'name=value'. The following options are valid:
            type= B|E|X|C : Required option, specifies the type of trace to be run. 
            at= true|false : Optional, instructs the test runner to append each trace to the previous trace, creating a single trace file for multiple test cases.
            trname=<filename>: Optional, instructs the test runner to name the trace file 'filename.tr' instead of the default 'instout.tr' (do not include the .tr extension) 
  
            Invoke the test runner on a tracing basic blocks test case and capture the output directly with redirection:
       java junit.textui.SelectiveTestRunner -sID 5 -t type=B subject.tests.ATestSuite >& t5
            Run multiple test cases, creating cumulative trace file
       javajunit.textui.SelectiveTestRunner-sID1-5-ttype=EXC,at=true   subject.tests.ATestSuite
  

Known Issues

Tracing the recursive case (running JUnit tests for instrumented JUnit itself) will not give correct results. The test selection classes subclass the instrumented classes, causing trace data to be recorded which represents the execution of the invoking environment as well as the test cases themselves.
Creation of traces and saving of outputs will NOT work with test suites built using the junit.extensions.ActiveTestSuite class. The test runner depends on the sequential execution of the test cases, an assumption which is violated by the ActiveTestSuite class.