Skip to content

Releases: randycoulman/mix_test_interactive

v1.1.0

08 Oct 20:57
6ce4ea1

Choose a tag to compare

Fixed

  • The p (pattern) command now works properly in umbrella projects. Previously, it was unable to find any test files in order to filter the pattern and would therefore not run any tests. Now, in an umbrella project, mix test.interactive looks for test files in apps/*/test by default, but still respects the :test_paths config option used by mix test. (#48)

Documentation

  • Fixed the spelling of Louis Pilfold's name in the README. Sorry, Louis! 🤦‍♂️ (#49)

v1.0.1

09 Mar 22:19
a7411c3

Choose a tag to compare

Fixed

  • Eliminates a GenServer call timeout that can occur if a command is typed while a long-running test run is in progress. (#44).

v1.0.0

18 Feb 16:27
daf160e

Choose a tag to compare

🎉 Happy Birthday!

The following sections describe changes from mix-test.watch, which served as the basis of this project.

Added

  • Interactive mode allows dynamically filtering test files based on a substring pattern or switching to run only failed or stale tests without having to restart.

  • File-watching mode can be turned on and off, either by passing --no-watch on the command line, or by using the w command to dynamically toggle watch mode on and off. When file-watching mode is on, tests will be run in response to file changes as with mix-test.watch. When off, tests must be run explicitly using the Enter key or by using another command that changes the set of tests to be run.

Removed

  • It is no longer possible to customize the CLI executable. We always use mix. Previously, this allowed the use of iex -S mix instead, but that doesn't work well with interactive mode.

  • It is no longer possible to specify multiple tasks to run on file changes. This ability added complexity and the feature didn't work very well because it assumed that all tasks would take the exact same set of command-line arguments. It is still possible to specify a different task name than test, but mix test.interactive assumes that the custom task accepts the same command-line arguments as mix test.

Fixed

  • On Windows, mix test.interactive runs the correct mix task, including a custom task provided in the configuration, rather than always running mix test. It also passes along other provided command-line arguments as well as those injected by mix test.interactive.