java emmarun [(1) EMMA options] -cp classpath... class [args...]
java emmarun [(1) EMMA options] -jar jarfile [args...]
(1) [-f] [-ix filter patterns...] [-r report types...] [-sp sourcepath...] [-raw] [-out session data file] [-merge boolean] [common options]
alternative form:
java emma run {same as above...}
-f, -fullmetadata
-ix, -filter filter patterns...
-r, -report (txt|html|xml)...
-sp, -sourcepath list of source directories...
-raw, -sessiondata
-out, -outfile session data file
-merge (y[es]|n[o])
report generation options...
Unlike its ANT equivalent, emmarun command line tool does not have dedicated options for controlling coverage report generation. If necessary, they can be set using generic -D, -properties, and other mechanisms.
So, for example, to change the default location of the HTML report you would override the report.out.file property:
>java emmarun -Dreport.html.out.file=mycoveragedir/myfile.html ...(report.html.out.file can be abbreviated to report.out.file if the command generates a single report type)
Run an application and generate plain text and XML reports with default parameters:
>java emmarun -r txt,xml -jar SwingSet2.jar
Run an application and generate an HTML report with some customization and linking to the application source code:
>java emmarun -r html -Dreport.columns=name,method,line -sp src/ -jar SwingSet2.jar
Run an application and don't generate any reports, just dump the raw coverage session data:
>java emmarun -raw -jar SwingSet2.jar
The default EMMA command line tool behavior is not to use System.exit() on exit unless an explicit -exit option is specified. If that is done, the error codes returned via System.exit() are as follows:
0 | Successful completion. |
1 | Failure due to incorrect option usage. This error code is also returned when command line usage (-h) is requested explicitly. |
2 | All other failures. |