Christoph Sturm
Christoph Sturm
to reproduce you can use an opensource project of mine, and set pitest version to 1.6.1 here: https://github.com/christophsturm/r2dbcfun/blob/main/build.gradle.kts#L154
strange thing is that with the build file from functest it works. in my own project can put anything into pitestVersion, and when i run gradle dependencies it still shows...
I think I found the reason. it only happens with the kotest pitest plugin. probably it has a dependency on pitest and that is stronger than the pitest version that...
ok so its a gradle problem? is there anything i can do to filter out updates for the bom? ``` The following dependencies have later milestone versions: - io.r2dbc:r2dbc-bom [Arabba-SR8...
this is how the class looks in "show kotlin bytecode": https://gist.github.com/christophsturm/1f46f14dde1a61a14ce449b0632f883c
right now i can't use pitest at all, so just reading the annotation would be a huge improvement even if we don't mutate anything. the coroutines code is just inlined...
btw, if pitest needs a line number for every non synthetic method, I wonder how it works with kotlin data classes, those have methods like toString and equals, which are...
serialization works, but i haven't tried with any other 3rd party plugin. I also found this issue which describes the problem https://youtrack.jetbrains.com/issue/KT-25596
it probably would need to be test runner specific. all expectations in a test case need to be registered and then checked afterwards. or you could use a threadlocal where...
this means there is no jmh plugin that works with gradle 4.0