The name originally came from a trawl of words containing test - and so should be pronounced as if it has the sense 'smallest'.
However, when @duncanmcg read back his first message on the subject I'd like to run my new test framework past you, he realised that there was another pronunciation - 'My New Test', and that is the emphasis that seems to have stuck.
See the readme
See the readme
There is experimental support for running tests with JUnit 4 - see JUnit4MinutestsTests
Understanding fixtures is key to Minutest - read more
There is experimental support for skipping some tests and only running others
Test Driven to Specification with Minutest - Part 1
Test Driven to Specification with Minutest - Part 2
JUnit Rules mostly work.
It's easy to integrate Okeydoke - see Minutest Examples
You can easily populate a fixture with the same annotations you would use in JUnit - see Minutest Examples
Annotate the method with dev.minutest.Tests, Alt-Enter on the greyed-out method and select Suppress unused warning if annotated by 'dev.minutest.Tests'. Now all @Tests methods should not be greyed out.
More elaborate tests with coroutines
You can use before, after and afterAll blocks in a context to manage resources.
For simple cases there is a closeableFixture block
The best bet for feedback and help is the #minutest channel on the Kotlin Slack. See you there.
TODO - in the meantime just ask.
TODO - in the meantime just ask.
TODO - in the meantime just ask.
TODO - in the meantime just ask.