v4.1.2

Updated

• Update README with instructions for running mix test.interactive as an independent script that doesn't require installing as a dependency in your application. (#127 - Thanks @andyl!)

• Allow process_tree versions v0.1.3 and v0.2.0 to provide more flexibility for upstream projects (#128)

v4.1.1

Fixed

• Properly handle mix test.interactive <files_or_patterns...> case. The new command-line parsing added in v4.0 was not properly capturing the filenames/patterns and passing them on to mix test. (#123 - Thanks @jfpedroza for finding and reporting the bug!)

v4.1.0 - More commands!

Added

• This version adds a number of new commands for controlling additional mix test options interactively:

  • d <seed>/d: Set or clear the seed to use when running tests (mix test --seed <seed>). (#112)
  • i <tags...>/i: Set or clear tags to include (mix test --include <tag1> --include <tag2>...). (#113)
  • o <tags...>/o: Set or clear "only" tags (mix test --only <tag1> --only <tag2>...). (#113)
  • x <tags...>/x: Set or clear tags to exclude (mix test --exclude <tag1> --exclude <tag2>...). (#113)
  • m <max>/m: Set or clear the maximum number of failures to allow (mix test --max-failures <max>). (#116)
  • r <count>//r: Set or clear the maximum number of repeated runs until a test failure (mix test --repeat-until-failure <count>). NOTE: mix test only supports this option in v1.17.0 and later. (#118)
  • t: Toggle test tracing on/off (mix test --trace). (#117)

• There is now a MixTestInteractive.TestRunner behaviour for use in custom test runners. Up until now, custom test runners needed to implement a single run/2 function. This release adds a behaviour that custom test runners can implement to ensure that they've correctly conformed to the interface. Custom test runners don't have to explicitly implement the behaviour, but must implicitly do so as before. (#115)

v4.0.0 - Config-less Operation

💥 BREAKING CHANGE 💥

This version introduces the option of "config-less" operation. All configuration settings can now be supplied on the command-line instead. To avoid confusion and clashes with mix test's command-line options, it is now necessary to separate mix test.interactive's options from mix test's options with -- separator.

For example, to use the new --clear option as well as mix test's --stale option, it is necessary to use:

mix test.interactive --clear -- --stale

This affects two of the command-line options that were available in previous versions:

• mix test.interactive's --no-watch flag. Previously, you could run (for example) mix test.interactive --no-watch --stale. This will no longer work. You must now use mix test.interactive --no-watch -- --stale instead.
• mix test's --exclude option. mix test.interactive now has its own --exclude option. Previously, you could run (for example) mix test.interactive --exclude some_test_tag and that argument would be forwarded on to mix test. Now you must use mix test.interactive -- --exclude some_test_tag instead.

If you don't use either of these two options, everything should work as before.

To upgrade to this version, you'll need to update any mix aliases or other scripts you may have defined for mix test.interactive. In addition, you and everyone who works in your codebase will need to update any shell aliases they have defined.

Added

• This version introduces the option of "config-less" operation. All configuration settings can now be supplied on the command-line instead. See the README or run mix help test.interactive for more information. Also, see the 💥 BREAKING CHANGE 💥 section above. (#108)

Changed

• The Running tests... message that mix test.interactive displays before each test run is displayed in color. This makes it easier to find the most recent test run when scrolling back in your shell. (#109)

v3.2.1

Fixed

• Fixed handling of custom command/args on Unix-like systems. mix_test_interactive was not correctly ordering the various arguments. (#105 - Thanks @callmiy!)

v3.2.0

Changed

• Made pattern matching more flexible. Previously, when given multiple patterns, we would not do any file filtering if any of the patterns was a file:line-style pattern. Instead, we'd pass all of the patterns to mix test literally. Now, we run normal file filtering for any non-file:line-style patterns and concatenate the results with any file:line-style patterns. (#99)
• Added documentation for missing configuration options in the mix task's module documentation. (#100)

v3.1.0

Added

• Add a new command configuration option that allows use of a custom command instead of mix for running tests. See the README for more details. (#96)

Changed

• Added documentation for missing configuration options in the README. (#96)

v3.0.0

💥 BREAKING CHANGE 💥

• This release drops support for Elixir 1.12. We officially support the same versions as Elixir itself, so support for Elixir 1.12 has been dropped. (#94)

There are no actual breaking changes in the code itself, so as long as you're on Elixir 1.13 or later, you should have no problems upgrading to this version.

Changed

• Update to the latest version of ex_doc. The documentation reflects these changes. (#93)

v2.1.0

Fixed

• Fix compiler warnings on Elixir 1.17. (#89 - Thanks @jfpedroza!)

v2.0.4

Fixed

• Ignore some filesystem events emitted by inotify. Some events are triggered later than others and end up causing the tests to run twice for a single file change. (#86 - Thanks @jwilger!)