Suppress jqwik output

[martinmladenov]

jqwik prints its output to the console and this output is not suppressed, which fills up the console when running property-based tests via the maven plugin

[Arraying]

This is explicitly enabled in RunJUnitTestStep.java line 45. What was the reason for enabling it? Perhaps we could enable/disable depending on where Andy is being run from.

[martinmladenov]

This is explicitly enabled in RunJUnitTestStep.java line 45. What was the reason for enabling it? Perhaps we could enable/disable depending on where Andy is being run from.

It looks like it was enabled in 5833b94

@mauricioaniche Do you know why that could be?

[mauricioaniche]

I think we wanted the message from jqwik when the property failed. But not the extra useless info that it prints when running the tests. Does that make sense?

[Arraying]

Guys, I think we could solve this by also solving a more general problem. Right now, we can run Andy through WebLab, through the Maven plugin or the command line/IntelliJ. But I think it's unclear how it is run. Perhaps we could specify a "runner" system property that:

• When called through the Docker image just does a -Drunner=weblab
• When called through the Maven plugin just does a System.setProperty("runner", "plugin")
• Or, when in main it notices no property set it defaults to System.setProperty("runner", "cli")

Then, we could set jqwik.reporting.usejunitplatform to true if we are using "weblab" otherwise to false. How does that sound?

[martinmladenov]

I don't see how this would be useful here - we don't need to print this information regardless of the environment.

[Jaswar]

The reason why I enabled jqwik.reporting.usejunitplatform was to get the output of JQWik - it was the only way I could find. By default it would print the whole output to the console. It was also important to show to the student the JQWik-found inputs that caused the errors and not only the assertion error message.
Unfortunately as you noted, the whole message is displayed including the run configuration, as this is what JQWik returns as the test fail reason.
Here is the whole discussion when developing this feature:
https://3.basecamp.com/4338320/buckets/22606949/todos/3837602898
https://3.basecamp.com/4338320/buckets/22606949/todos/3985404747

I also posted an issue about it on JQWik GitHub page:
jqwik-team/jqwik#209

Maybe by utilizing the other method suggested by the author of JQWik, we could extract only the relevant parts of the message.

[mauricioaniche]

Is this ticket still valid?