The --no-color and --color flags (to disable and force colors) now work again (regression in 0.19.1-revision5).
--no-color now turns off colors in Elm compiler error messages as well.
0.19.1-revision5 - 2020-01-28
Breaking
Removed support for Node.js 8 (which reached end of life 2019-12-31). Node.js 10.13.0 is now the minium supported Node.js version.
Removed the undocumented --verbose flag. It didn’t do much at all in its current state.
Fixed
Now works on Apple Silicon/M1/ARM MacBooks. Installation used to fail with “Error: No binaries are available for your platform: darwin-arm64.”
You can now run your test from a subdirectory. elm-test finds your elm.json up the directory tree instead of printing an error.
If you had a port named send or receive and they were reached via test cases, elm-test used to fail with a duplicate port error. elm-test has renamed its internal ports so that conflicts are very unlikely.
The JUnit reporter now says @failures instead of @failed which makes Jenkins happier.
elm-test now errors on unknown (misspelled) flags instead of silently ignoring them.
elm-test now errors on bad --fuzz and --seed values instead of silently ignoring them.
A whole host of Elm package dependencies errors, by using elm-json to calculate the set of dependencies needed to run your tests.
elm-test --watch no longer crashes if for packages if there are compilation errors in src/ at startup.
elm-test --watch now detects changes in your elm.json.
elm-test --watch now works better when lots of files change at once. If 10 files changed, your tests used to run 10 times in sequence (more or less). Now, they only run once or twice. Changes within 100 ms are batched together. Changes happening while the tests are running no longer queue up – they instead trigger one single test once the current run is done.
Compilation errors are no longer hidden by a super long “Compilation failed while attempting to build [absolute paths to every single test Elm file]” message.
A bunch of checks and validations have been added to help in edge cases.
Performance
elm-test is now faster to install (by having fewer dependencies). It used to be around 18 MB, now it’s just 2 MB.
elm-test now runs about half a second faster, by no longer using elmi-to-json. (As a bonus, if you ever encountered errors mentioning elmi-to-json, that won’t happen anymore.)
elm-test --watch now reruns your tests sooner after file changes (about 100 ms after the changes, instead of about 500 ms).
Changed
The --help output is now more conventional and hopefully easier to read.
The --no-color and --color flags (to disable and force colors) now work again (regression in 0.19.1-revision5).
--no-color now turns off colors in Elm compiler error messages as well.
0.19.1-revision5 - 2020-01-28
Breaking
Removed support for Node.js 8 (which reached end of life 2019-12-31). Node.js 10.13.0 is now the minium supported Node.js version.
Removed the undocumented --verbose flag. It didn’t do much at all in its current state.
Fixed
Now works on Apple Silicon/M1/ARM MacBooks. Installation used to fail with “Error: No binaries are available for your platform: darwin-arm64.”
You can now run your test from a subdirectory. elm-test finds your elm.json up the directory tree instead of printing an error.
If you had a port named send or receive and they were reached via test cases, elm-test used to fail with a duplicate port error. elm-test has renamed its internal ports so that conflicts are very unlikely.
The JUnit reporter now says @failures instead of @failed which makes Jenkins happier.
elm-test now errors on unknown (misspelled) flags instead of silently ignoring them.
elm-test now errors on bad --fuzz and --seed values instead of silently ignoring them.
A whole host of Elm package dependencies errors, by using elm-json to calculate the set of dependencies needed to run your tests.
elm-test --watch no longer crashes if for packages if there are compilation errors in src/ at startup.
elm-test --watch now detects changes in your elm.json.
elm-test --watch now works better when lots of files change at once. If 10 files changed, your tests used to run 10 times in sequence (more or less). Now, they only run once or twice. Changes within 100 ms are batched together. Changes happening while the tests are running no longer queue up – they instead trigger one single test once the current run is done.
Compilation errors are no longer hidden by a super long “Compilation failed while attempting to build [absolute paths to every single test Elm file]” message.
A bunch of checks and validations have been added to help in edge cases.
Performance
elm-test is now faster to install (by having fewer dependencies). It used to be around 18 MB, now it’s just 2 MB.
elm-test now runs about half a second faster, by no longer using elmi-to-json. (As a bonus, if you ever encountered errors mentioning elmi-to-json, that won’t happen anymore.)
elm-test --watch now reruns your tests sooner after file changes (about 100 ms after the changes, instead of about 500 ms).
Changed
The --help output is now more conventional and hopefully easier to read.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps elm-test from 0.19.1-revision4 to 0.19.1-revision6.
Release notes
Sourced from elm-test's releases.
Changelog
Sourced from elm-test's changelog.
Commits
bd29dbc0.19.1-revision6d6bc663release revision 6 - hotfix for colors5ef1482Fix --no-color (#491)b948183Prepare revision 5! (#490)224fe29Add changelog for the next release (#487)a211d34Remove odd line in compile errors (#488)995b916Improve readme and --help (#473)fbb6f2aUpgrade to commander 7 (#486)4b17314Update elm-review (#485)1ef0746Update elm-tooling to 1.0.0 (#482)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)