3 ms·
Yes you can (I managed it and it works beautifully). But you have to make it ignore Package Class at the moment because top functions in a package (say my.grea
by lakedaemon 11y ago
Yes you can (I managed it and it works beautifully).
But you have to make it ignore Package Class at the moment because top functions in a package (say my.great.pack) can be in different .kt files and are gathered in a single class (my.great.pack.PackPackage) and pit doesn't seem to be able to cope with a class whose source come from more than 1 file (or I missed something).
Just put something like this in your gradle.build file :
apply plugin: "info.solidsoft.pitest"
pitest {
targetClasses = ['org.lakedaemon.suggest.', 'org.lakedaemon.compress.']
//by default "${project.group}."
excludedClasses = ['org.lakedaemon.compress.decoders.DecodersPackage', 'org.lakedaemon.compress.decoders.EncodersPackage']
avoidCallsTo = ['org.apache.log4j.', 'org.lakedaemon.L.', 'org.slf4j.', 'java.util.logging.']
pitestVersion = "1.1.4" //not needed when a default PIT version should be used
threads = 4
outputFormats = ['XML', 'HTML']
enableDefaultIncrementalAnalysis = true
testSourceSets = [sourceSets.test/, sourceSets.integrationTest/]
mainSourceSets = [sourceSets.main/, sourceSets.additionalMain*/]
}