Johannes Link
Johannes Link
> Would it work for reproducing CI failures? If you keep the jqwik database around across runs, then yes. It may be useful, though, to have an explicit way of...
Is it in the context of stateful generation?
To be frank, I’ve never considered that case: sample recreation for action sequences. Now that I do, it seems obvious that it cannot work as is. Since building up the...
If that can bridge the shortcomings of the current stateful generation it's probably worthwhile.
Might be interesting to know that I implemented @IRus' suggestion in jqwik.net. With the extension point (aka lifecycle hook) for invokeMethods present, the implementation is rather simple: https://github.com/jlink/jqwik/blob/main/kotlin/src/main/kotlin/net/jqwik/kotlin/internal/SuspendedPropertyMethodsHook.kt @IRus I...
> I wonder how you work around discovery issue: `suspend` methods returns `Object` jqwik doesn't have that problem since it allows any return type in test/property methods.
Is it in scope for Alpha1 (end of next week)?
Why not use preconditions as the concept to determine the order? A step can have none, one or many. A runner could thereby parallelize test execution as much as possible....
Sounsd like a good use case for a test engine of your own? I wouldn't like to overload the meaning of @Test within the JUnit 5 engine. > Am 31.12.2015...
> Add a mode where ArbitraryImpl, Combinator, etc would capture stacktrace (or just the most top frame excluding certain library-specific ones), so Arbitrary#toString could provide the source code location where...