Changelog
0.7.1
- Slightly better reporting for exceptions raised unexpectedly in
FlowAssertions.TabularA.run_and_assert/2.
0.7.0
FlowAssertions.TabularAfor tabular tests that are more broadly useful thanFlowassertions.Define.Tabular, which is for testing assertion definitions.- Friendly error messages when arguments to
FlowAssertions.Checkers.in_any_order/1are notEnumerable.
0.6.1
Fixes
FlowAssertions.Checkers.in_any_orderfailed to produce a correct assertion message if a mismatching Enumerable contained a value that didn't implementString.Chars.
0.6.0
Additions
Flowassertions.Define.Tabularfunctions now have a stable enough API to use safely.FlowAssertions.Define.Tabular.nonflow_assertion_runners_for/1FlowAssertions.Checkers.has_slice/1
Tweaks
FlowAssertions.Define.BodyParts.adjust_assertion_error/2now combines bothputandupdate!behavior for replacements.
0.5.0
Additions
Tweaks
FlowAssertions.Define.BodyParts.struct_must_have_key!/2has a better error message.
0.4.0
Features
Checkers work with
FlowAssertions.MiscA.assert_good_enough/2in a way that allows better error messages.FlowAssertions.MiscA.ok_content/2Like
FlowAssertions.MiscA.ok_content/1, but takes a second, name argument. The content must be a struct with that name (a module).FlowAssertions.EnumA.singleton_content/2Like
FlowAssertions.EnumA.singleton_content/1, but takes a second, name argument. The content must be a struct with that name (a module).FlowAssertions.Define.BodyParts.elaborate_refute/3A variant of
ExUnit.Assertions.refute/1that allows creation of specialized error messages.
Deprecations
- Deprecate
FlowAssertions.NoValueA.refute_no_value/3in favor ofFlowAssertions.NoValueA.assert_values_assigned/3