Closed sbuisson closed 6 years ago
I do a pull request to correct this issue: https://github.com/VinodAnandan/sonar-pitest/pull/17 The pull request pass, the issue in the build is that the sonar cannot be reach.
@sarahBuisson I'm afraid the test coverage over new code has dropped, and in reviewing further, we don't have any unit tests with kotlin mutations in the mutations.xml file.
I looked over at the pitest project and couldn't find any examples there either. Would you be able to provide a mutations.xml file generated from pitest generating mutations on kotlin source?
@bradflood I don't understand. Do you want I add test to my PR , or do you just want a mutation.xml?
`<?xml version="1.0" encoding="UTF-8"?>
`
@sbuisson sorry I wasn't very clear. What you provided is perfect - I'm not familiar with Kotlin and wanted to understand how pitest reported on Kotlin mutations, specifically the mutatedClass and the sourceFile elements. It appears there is no correlation. I'm getting ready to refactor to create SQ issues and need to create some Kotlin tests before I start.
@sbuisson the just-completed 0.9-SNAPSHOT build has what I believe is first-class support for mutations in Kotlin code. Could you please evaluate and give feedback on whether Kotlin files show mutation info? They will show as Issues with tags "test-quality" and "test-coverage"
I've a project with a mix of kotlin and java file, only the java files are displayed on the Mutation analysis Measures page.
Just for info: both my java and kotlin file are present in the pitest report: `Main.java some.Main main ([Ljava/lang/String;)V 10 org.pitest.mutationtest.engine.gregor.mutators.VoidMethodCallMutator 5 removed call to java/io/PrintStream::println
`