run_mutation.pl -- mutation analysis for generated test suites.
run_mutation.pl -p project_id -d suite_dir -o out_dir [-f include_file_pattern] [-v version_id] [-t tmp_dir] [-D] [-A]
project_id
The id of the project for which the generated test suites are analyzed. See Project module for available project IDs.
The directory that contains the test suite archives. See Test suites.
The output directory for the results and log files.
include_file_pattern
The pattern of the file names of the test classes that should be included (optional). Per default all files (*.java) are included.
version_id
Only analyze test suites for this version id (optional). Per default all test suites for the given project id are analyzed.
The temporary root directory to be used to check out program versions (optional). The default is /tmp.
Debug: Enable verbose logging and do not delete the temporary check-out directory (optional).
All relevant classes: Perform mutation analysis for all relevant classes (i.e., all classes touched by the triggering tests). By default only classes modified by the bug fix are analyzed.
Performs mutation analysis for each provided test suite (i.e., each test suite archive in suite_dir) on the program version for which that test suite was generated. Each test suite has to pass on the program version for which it was generated.
The results of the analysis are stored in the database table out_dir/TAB_MUTATION. The corresponding log files are stored in out_dir/TAB_MUTATION_log.
By default, the script logs all errors and warnings to run_mutation.pl.log in the temporary project root. Upon success, the log file of this script and the detailed mutation results for each executed test suite are copied to: out_dir/TAB_MUTATION_log/project_id.
To be considered for the analysis, a test suite has to be provided as an archive in suite_dir. Format of the archive file name:
project_id-version_id-test_suite_src(\.test_id)?\.tar\.bz2
Note that test_id
is optional, the default is 1.
Examples: