jwstegemann
Evaluate migrating to a better test framework
As the development of fritz2 started, the infrastructure for multiplatform projects was rather poor, as it was bleeding edge and lots of alpha status.
Meanwhile the ecosystem has evolved and there might be better choices for writing automated tests than the built-in test framework. The latter is rather weak when it comes to:
- assertions (not expressive, no custom matchers, no grouping / multi assert)
- data driven tests
- property based testing is not supported at all
- output rather limited (in failure case)
We should investigate, which frameworks are popular in the Kotlin multiplatform world and then pick one and try to invest two days or so to get a feeling, how much work it will be to migrate all our tests.
Frameworks (Please add):
Kotest is currently unsuable with JS IR: https://github.com/kotest/kotest/issues/2163
Kotest 5.0 will support JS IR. It's already working in a feature branch and 5.0 will probably drop in around 4 weeks. The caveat is that 5.0 will DROP support for JS legacy (but that's going away anyway).
