hmLoadTopic({ hmKeywords:"Arguments,Arguments command line overview,Command line,Command line examples,Command line interface overview,Command line unrecognised arguments,Examples,Examples command line", hmTitle:"Command Line Interface", hmDescription:"Coverage Validator provides a command line interface to allow you to perform automated coverage data collection.", hmPrevLink:"environmentvariables.html", hmNextLink:"example-command-lines.html", hmParentLink:"index.html", hmBreadCrumbs:"", hmTitlePath:"Command Line Interface", hmHeader:"
<\/p>\n\r
Coverage Validator provides a command line interface to allow you to perform automated coverage data collection.<\/p>\n\r
<\/p>\n\r
To run 32 bit coverage validator run C:\\Program<\/span> <\/span>Files<\/span> <\/span>(x86)\\Software<\/span> <\/span>Verify\\Coverage<\/span> <\/span>Validator<\/span> <\/span>x86\\coverageValidator.exe<\/span><\/p>\n\r <\/p>\n\r To run 64 bit coverage validator run C:\\Program<\/span> <\/span>Files<\/span> <\/span>(x86)\\Software<\/span> <\/span>Verify\\Coverage<\/span> <\/span>Validator<\/span> <\/span>x64\\coverageValidator_x64.exe<\/span><\/p>\n\r <\/p>\n\r <\/p>\n\r <\/p>\n\r Potential uses for automated code coverage analysis are:<\/p>\n\r <\/p>\n\r •<\/span>In the regression test suite to ensure code coverage of a certain level <\/span><\/p> •<\/span>In unit testing to ensure code coverage of a certain level<\/p> •<\/span>Quality assurance<\/p> <\/p>\n\r Results from coverage data collection sessions can be merged to form an aggregate result.<\/p>\n\r <\/p>\n\r Typically, command line options allow Coverage Validator to run by specifying:<\/p>\n\r <\/p>\n\r •<\/span>the target program to run <\/span><\/p> •<\/span>arguments to pass to the target program<\/p> •<\/span>the working directory to run in<\/p> •<\/span>whether to run with or without the user interface<\/p> •<\/span>a baseline session to compare with<\/p> •<\/span>where and how to save results<\/p> •<\/span>what to include or exclude from hooking<\/p> •<\/span>how to merge results <\/span> Usually Coverage Validator would exit between automated tests, but it can be made to stay running if necessary.<\/p>\n\r <\/p>\n\r <\/p>\n\r <\/p>\n\r <\/p>\n\r There are a few basic rules to remember when using the command line arguments:<\/p>\n\r <\/p>\n\r •<\/span>separate arguments by spaces •<\/span>quote arguments if they contain spaces •<\/span>some arguments are only useful in conjunction with others •<\/span>some arguments are incompatible with others<\/p> <\/p>\n\r If your command line is very long, consider using -commandFile<\/span> to specify a command file for your arguments.<\/p>\n\r <\/p>\n\r <\/p>\n\r Any unrecognised arguments found on the command line are simply ignored, whether or not they are prefixed with a hyphen.<\/p>\n\r <\/p>\n\r Arguments intended for your program will not conflict with the Coverage Validator arguments in this manual as you should use -arg<\/a> (or -allArgs) to redirect them to your program.<\/p>\n\r <\/p>\n\r <\/p>\n\r <\/p>\n\r<\/a>Automated coverage data collection<\/span><\/h1>\n\r
\n\r <\/span><\/p>See the command line reference<\/a> for an alphabetical listing all the available commands.<\/h1>\n\r
Command line argument usage<\/span><\/h1>\n\r
\n\r <\/span><\/p>
\n\r <\/p>
\n\r <\/p>Unrecognised arguments<\/span><\/h1>\n\r
<\/span><\/h1>\n\r
Need some help building the command line?<\/span><\/h1>\n\r