-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for elm-test-rs #19
Comments
I don't mind using whatever is more convenient. For the time being I'm making elm-test-rs releases manually so I can easily change the compression format.
I don't intend to make frequent releases after 1.0.0. There might be a couple releases before that, depending on what bugs people find and completion of some features like the json and junit reports that are not finished (I haven't touched those since march or april). After that, the current set of features is enough for my usage, so updates will mostly be contributor-based or security patch I suspect. |
I just published version 0.5 with some fixes: https://github.com/mpizenberg/elm-test-rs/releases/tag/v0.5 |
Yes, that’ll mean less coding on the elm-tooling side. All that should be needed is adding |
This is the plan:
|
The reason for 1 is, that you would need to patch the cli each time something is released? |
@razzeee Correct! |
Just a note to let you know that a month may pass without a version because I'm busy at work now. But a new version is intended after that in the coming weeks. |
This involves:
unzip
executable if it’s available – it seems to be available on Alpine Linux. Alternatively, convince @mpizenberg to use .gz or .tgz, at least on non-Windows. EDIT: Next version is .tar.gz, should be easy to do.elm-tooling init
should include elm-test-rs or not. Currently that command includes the latest version of all known tools, but maybe we don’t want to include elm-test-rs until it’s considered more stable or is more popular.The text was updated successfully, but these errors were encountered: