Changelog History
-
v0.10.1 Changes
December 17, 2024 -
v0.10.0 Changes
November 07, 2024Mneme v0.10.0 is now available
๐ This release adds
mix mneme.test, a basic wrapper aroundmix testthat allows Mneme's configuration options to be passed at the command line in addition to all the options normally accepted when running tests. Additionally,mix mneme.watchnow wrapsmneme.testand therefore takes the same options.I recommend you add
:"mneme.test"to your:preferred_cli_envinmix.exs:defprojectdo[...preferred\_cli\_env: ["mneme.test": :test,"mneme.watch": :test],...]endโก๏ธ You can also simply run
MIX_ENV=test mix mneme.installto update your setup. -
v0.9.3 Changes
October 21, 2024 -
v0.9.2 Changes
October 14, 2024Mneme v0.9.2 is now available.
โ Added
- โ Added
--exit-on-successflag tomix mneme.watch, which reruns tests until all of them pass, then exits.
๐ Fixed
- ๐ Prevent an increasing number of "Running ExUnit with seed..." messages from printing during runs of
mix mneme.watch. This was a regression introduced in v0.9.1.
- โ Added
-
v0.9.1 Changes
October 14, 2024 -
v0.9.0 Changes
October 14, 2024Mneme v0.9.0 is now available.
๐ This release introduces a new, automatic test runner and watcher,
mix mneme.watch. It can be used instead of or in addition tomix test. When run, it will watch both source and test files, automatically re-running tests on change. It knows how to interrupt Mneme prompts, so you can use it to very quickly iterate on something, immediately seeing the new patterns as you save files. -
v0.8.2 Changes
July 11, 2024Mneme v0.8.2 is now available.
๐ This release includes a couple of bug fixes and one small CLI feature.
๐ There were some regressions in the last few releases relating to map patterns that could cause many duplicate patterns to be suggested and, in some cases, incorrect patterns that wouldn't match your actual value. I believe these are now fixed, but please let me know if you run into any weird suggestions!
Two new key bindings have been added to the CLI:
JandKto jump to the first or last pattern. This can be helpful especially when you have a large, nested data structure, as these can cause Mneme to generate quite a few patterns at various levels of complexity.
-
v0.8.0 Changes
June 20, 2024v0.8.0 is now available
Thanks to @am-kantox, issue #1 has been closed: variables bound in
auto_assertpatterns are now accessible outside of the expression! This was the main limitation of Mneme vs. plainExUnitassertions, so I'm very thankful that it's been resolved.๐ Prior to this release, you had to use the return value of
auto_assertto access anything you were testing. Now, you can bind the result or portions of it inside the assertion pattern:# previously...result=auto\_assert%{x: 1}\<-some\_function()# now...auto\_assert%{x: 1}=result\<-some\_function()# ^^^^^^# this would previously be a warning or errorauto\_assert%{x: x}\<-some\_function()# ^# destructuring works as expected