Match a method to this pattern if its number of aggregated statements is not greater than maxAggregatedStatements. Aggregated complexity metric is a sum of the method complexity and complexity of all anonymous inline classes declared in the method. In other words - all methods with aggregated complexity <= maxAggregatedComplexity will be filtered out. Match a method to this pattern if its aggregated cyclomatic complexity is not greater than maxAggregatedComplexity. In other words - all methods with statements <= maxStaments will be filtered out. Match a method to this pattern if its number of statements is not greater than maxStatements. In other words - all methods with complexity <= maxComplexity will be filtered out. Match a method to this pattern if its cyclomatic complexity is not greater than maxComplexity. Note that when method signatures are tested against this regexp, whitespace is normalized and comments are ignored. This regexp should match the method signatures of methods you wish to include in this context. Must be unique, and not be one of the reserved context names (see Using Coverage Contexts).Ī Perl 5 Regexp that defines the context. This element, which supports both Java and Groovy, turns on Clover's distributed coverage feature, enabling the collection of per-test coverage data, when your test environment requires more than one JVM ( Java Virtual Machine). Use the ' clovercompiler' attribute instead. This means that builds that use the Clover 1.0 property set will continue to operate as expected.ĭo not set the ' compiler' attribute on the task as this overrides the Clover compiler set up by. The task provides a convenient method to set these properties. It is important to note that the Clover compiler adapter still picks up its settings from the set of Clover Ant properties. The directory into which Clover will write an instrumented copy of the source code. Note that setting the source attribute on the target will override this setting. The default source level to process source files at. This controls whether the initstring parameter is treated as a relative path or not. For more details please see ' Advanced Usage'. If set to ' false', test results will not be recorded instead, results can be added via the fileset at report time. No defaults to "all" in 3.2.2-4.0.2 and to "none" since 4.0.3.Ī boolean attribute which controls whether the instrumented source will be retained after compilation. See the Java 8 code instrumented by Clover fails to compile Knowledge Base article for more details. In such case disable instrumentation of expression-like form (i.e. "Math::abs" (option is available since Clover 4.0.5)ĭue to Clover's restrictions related with code instrumentation and javac compiler's type inference capabilities, you may get compilation errors when expression-like lambda functions are passed to generic methods or types. $"Īll_but_reference - instrument lambdas written in any form except method references, e.g. Typically this is a relative or absolute file reference, e.g. The Clover initString describes the location of the Clover coverage database. If false, Clover will instrument source files without using fully qualified java.lang names. This should only be set to ' false' if you have defined a variable called 'java' in your source files. This is an 'active' mode in that flushing occurs on a separate thread and is not dependent on the execution of instrumented code.įor more information, see Using a Flush Policy. Threaded - Coverage data is flushed as for directed, as well as periodically at a rate based on the value of flushinterval. This is a 'passive' mode in that flushing potentially occurs as long as instrumented code is being executed. Interval - Coverage data is flushed as fordirected, as well as periodically at a maximum rate based on the value of flushinterval. Valid values are directed, interval, or threaded.ĭirected - Coverage data is flushed at JVM shutdown, and after an inline flush directive. This attribute controls how Clover flushes coverage data during a test run. When the flushpolicy is set to interval or threaded this value is the minimum period between flush operations (in milliseconds) This attribute provides a convenient control point to enable or disable Clover from the command line. This controls whether Clover will instrument code during code compilation. If you wish to specify an alternative compiler, you can either set the piler property or use this attribute. It takes the same values as the standard Ant piler property. This attribute specifies the adapter to use. After instrumentation, Clover hands off compilation to the standard Ant compiler adapter (or the compiler specified by the piler Ant property).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |