Sam

This is likely because your console is not defaulting to UTF8. See the 1st answer here: https://stackoverflow.com/questions/24803733/default-character-encoding-for-java-console-output

If someone wants to create a plugin that would be great, but it's unlikely to be something the core kotest team tackles.

I can't duplicate with gradle 7.4.2. Which version of gradle are you using ? ``` > Task :template-server:test com.sksamuel.template.server.Level 0 > Level 1 > Level 2 > com.sksamuel.template.server.Level 0.Level 3.2...

And this is 5.3.2

@hosswald I cannot duplicate this. Is it still happening ?

We're unlikely to add a workaround for a bug in gradle 6.x due to the age of that release and the number of junit bugs it contains.

@myuwono I fancy adding something like this as the next step in the property test framework. What do you think ?

This works (not super advanced!) ```kotlin package com.sksamuel.kotest.property import io.kotest.matchers.shouldBe import kotlin.random.Random interface Action { fun run(input: T): T } fun Action.precondition(f: (T) -> Boolean): Action { return object :...

Good feedback, so I've updated my playground to this: ``` /** * A function that is applied against the current state to mutate and/or test. */ interface Action { /**...

I've opened a PR as a starting point.