The test option executes multiple Ruletest (.ert) files and their test sheets, and produces an output file with the test results.

Table 1. usage: corticonManagement --test
Argument Description
-i,--input file,... Required. A comma-separated list of the source Ruletest .ert files to run.
  • If there are spaces in the filenames or paths, then the entire set needs to be in quotes. Whitespace surrounding the comma character is valid. For example: 
    --input "C:\test\file1.ert , C:\test\file2.ert"
  • Wildcards can be used in the filename to allow greater flexibility in specifying multiple files with similar names. The wildcards (? and *) can only be used in the filename portion of the path and not any other parts of the path. Wildcards can be used in combination with the comma separated list. For example: 
    --input "C:\test\file?.ert , C:\test2\*.ert"
  • IMPORTANT: When the input option resolves to multiple files, then the sheet option cannot be used and the all option must be specified.
-o,--output file Required. Explicit path to the preferred output folder and existing file name (an XML file in the JUnit test output style that includes pass/fail, test suite, test file, and execution time.) The output file is never overwritten; instead, new test output is appended after test execution, thus enabling multiple executions of different test sets to log their output into a single report file.
-a,--all Required unless --sheet is stated. Runs tests for all the testsheets in the specified Ruletest in the order that they are defined in the file. Overrides any specific testsheets listed in the sheet option.
-s,--sheet sheet_names Required unless --all is stated. Runs tests for only the one or more (in a comma-separated list) specified testsheets in the Ruletest in the order that they are listed.
-dj,--dependentjars dependentJar1,... Comma separated list of dependent JAR paths. These are extra jar files that are needed to run the tests, such as those for extended operators, SCOs, ADC, and REST.
-ll,--loglevel level Sets the log level to the specified level of detail. Defaults to current server log level, typically INFO. Choosing DEBUG is verbose.
-lp,--logpath path Explicit path to the folder where CcManagement.log will be saved. Defaults to the server's current log location, typically [CORTICON_WORK_DIR]/logs.

Example usage:

corticonManagement --test -a
                   --input C:\MyTest.ert  
                    -o C:\MyTest_out.xml
corticonManagement -t 
                   -i "C:\MyTest.ert , C:\moreTests\*.ert" 
                   -o  C:\MyTest_out.xml 
                   -a 
corticonManagement -t -a 
                   -i "C:\Users\me\workspace\Generic\add*.ert,C:\test bed\base?.ert" 
                   -o C:\testOutput\Output.xml 
                   -ll DEBUG