1/31/2024 0 Comments Nexuiz mutators listList of globs to match against method names. CONSTRUCTOR_CALLS NON_VOID_METHOD_CALLS įor details of the available mutators and the default set applied see mutation operators. Whether or not to create mutations in static initializers. The number of threads to use when mutation testing. The distance filter is particularly useful when performing a targeted mutation test of a subset of classes withinĪ large project as it avoids the overheads of calculating the times and coverage of tests that cannot exercise the mutees. This filter will not work for tests that utilise classes via interfaces, reflection or other methods where the dependencies between classes cannot be determined from the byte code. , a test that calls a method on a class that uses the mutee as an implementation detail has a distance of 2 etc. e.g A test that directly calls a method on a mutated class has a distance of 1 PIT can optionally apply an additional filter to the supplied tests, such that only tests a certain distance fromĪ mutated class will be considered for running. Tests found via these suites can also be limited by the distance filter (see below). Custom suites such as ClassPathSuiteĪre supported. This parameter can be used to point PIT to a top level suite or suites. targetTestsĪ list of globs can be supplied to this parameter to limit the tests available to be run. In 1.2.0 and later versions, the classes to mutate are determined by scanning the maven output directory. If no targetClasses are supplied pitest will automatically determine what to mutate.īefore 1.2.0 pitest assumed that all code lives in a package matching the maven group id. Some features are enabled by default and must be disabled with -featureName, others must be enabled explicitly with +featureName. Additional features may be added by pitest plugins. Available options are shown in the console output when verbose logging is enabled. List of pitest features to enable or disable. The number of threads and list of mutation operators are both worth having a play with. PIT tries to work sensibly out of the box, but also provides many configuration options. If you need them you’ll have to either add a ‘*’ at the end of the glob to also match them ( * instead of ) or to add another rule for it ( .* in addition to ). But if you match exact class names, inner classes won’t be included. ![]() Globs are pretty simple and will work as expected as long as you match packages (like .want.to.mutate*). This goal does not currently guarantee to analyse changes made to non public classes that are not inner classes. To use this goal the maven scm plugin must be correctly configured for the project ![]() Mvn org.pitest:pitest-maven:scmMutationCoverage -Dinclude =ADDED,UNKNOWN -DmutationThreshold =85
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |