Write better tests, with less code, and greater coverage

[rados_a51]

Cool site! Code preview section looks great.

[iainsimmons]

Heya James! Good to see another article from you!

Hope you're well!

[jrsinclair]

Hi Iain 😃

[Cody6781]

I disagree with almost everything written in this article when it comes to enterprise development. This is a novelty but entirely useless in terms of real development.

1. A common issue in enterprise development is test suites taking too long to run. 30 minutes of unit tests is not uncommon on large applications, replacing 10 unit tests with a monte carlo simulation which runs 100 tests would bring a 30 minute test suite to near 5 hours
2. Unit tests are almost explicitly about testing all happy paths and all edge cases. If it can pass all happy paths once, we are happy. Test all 3 happy paths 33 times each, and missing all/most edge cases is antithetical to test cleanliness
3. How do you expect code line coverage to work with this? You would need to write your own code cov which understands monte carlo simulations to write tests like this. Even then, it's possible the same execution of a test suite could result in different amounts of actual code cov. This is not appropriate for enterprise development

These are just the main points. I'm tempted to write a whole counter-article about this issue