[Support] Running jqwik with pitest about jqwik HOT 7 CLOSED

Foreign IDs are now silently ignored.

Available in 1.2.0-SNAPSHOT

from jqwik.

So you know how to get rid of "No Jqwik properties file": Just add the file. Or reconfigure your logger to not print out INFORMATION level entries.

As for the WARNING level logs: In principal id's starting with [engine:junit-jupiter] shouldn't be forwarded to other engines besides Jupiter. I'll do some research and get back to you.

from jqwik.

@jlink Some more information:

The tests mentioned in the WARNING messsages are normal jupiter tests. The jqwik tests are defined in classes called *PropertiesTest

from jqwik.

@Serranya How do you run pitest? Through IDE, Gradle, Maven?

from jqwik.

@jlink Im running pitest through maven with the pitest-junit5 plugin

you should be able to reproduce the issue with this tree (java11 required) https://github.com/Serranya/de.serra.condorcat/tree/f85a862e99df4b50fe251d5abcf4802c02cedad1

from jqwik.

I had a look at pitest's junit 5 plugin. That's where the "problem" is located if you will. Pitest will refer each and every test method by its unique id. This will in the end lead to the warning from the jqwik test engine.

Since I'm going to reconsider jqwik's discovery mechanism for version 1.2.0 anyway, the warnings might go away or become DEBUG level logs. Until then, you should just ignore them.

from jqwik.

Ok, thanks for the promt support :)

jqwik is awesome.

from jqwik.