You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
raises a NoMethodError. In the context of this particular matcher, the use of a negative expectation should be very rare, but having it just not work will be surprising behaviour to the user.
The text was updated successfully, but these errors were encountered:
We misunderstood the MiniTest documentation and source; reversing (refuting) an assertion isn't controlled by the last parameter on infect_an_assertion; it's implemented using a second, reverse-logic assertion. 😖
The current implementation of assert_required_static_call_param actively verifies that the specified key occurs in the valid parameters for the subject class' .call method. This isn't a ten minute fix; kicking it down the calendar until resources permit or priorities demand.
Using the existing
must_require_initialize_parameter
MiniTest::Spec wrapper aroundMiniTest::Assertions:: AssertRequiresInitializeParameter
, we can have a positive expectation, but the use of:reverse
to enable negative expectations does not appear to be operative.That is,
works as expected, but
raises a
NoMethodError
. In the context of this particular matcher, the use of a negative expectation should be very rare, but having it just not work will be surprising behaviour to the user.The text was updated successfully, but these errors were encountered: