Model-Based Testing

I've actually used it very successfully in industry. The big value in my opinion is how it separates out thinking about your test data from your test cases. Instead of thinking about edge cases for particular functions, you think about what your data can possibly look like and then state what properties need to hold about it.

One tip for anyone trying out jqwik in an enterprise environment is to have static utility classes for generating Arbitrary<YourBusinessType> and then setup your data sources on a per test basis rather than setting defaults for the types globally. I find this makes it easier to manage cases where you have different constraints for common data types that needs to vary per suite of tests. For example, maybe in one case the dates need to be in the past while another suite of tests should be run over any possible date.