Closed Janiczek closed 2 years ago
I copied that trick from node-test-runner; its benefit for me is that I don't need to specify indirect dependencies in the elm.json file. Since I'm doing the changes by hand (can't really install elm-explorations/test 2.0.0 currently in any official way) there might have been a risk of doing something wrong. With the package elm.json files you just change 1.2.2 <= v < 2.0.0
into 2.0.0 <= v < 3.0.0
- smaller chance of getting something wrong.
@mpizenberg I've resolved the merge conflict; I've changed the valid testlib range to 2.0.0 <= v < 3.0.0 in this PR as well - hopefully that's the place to do it
Related to https://github.com/mpizenberg/elm-test-runner/pull/13
Added 5 new tests + one that combines them all:
These tests are not used in the end-to-end Rust test runner in any special way (they still do get picked up by it though). They are just a nice way to manually test the coverage scenarios. There's also a "kitchensink" coverage test project that contains all the scenarios at once, allowing you to see whether all the newlines etc. of the reporter are OK.