We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All methods which start with "assert_" or "refute_" are currently assumed to be (and counted as) Minitest assertions. E.g.
With Minitest/MultipleAssertions Max of 1 the following registers an offense.
Minitest/MultipleAssertions
def test_asserts_once assert_equal(:assert_equal, Bar.assert_but_not_a_minitest_assertion) end
No offense should be registered, as only one Minitest assertion is called in the test.
Offense is registered.
See above code sample
$ [bundle exec] rubocop -V 1.66.1 (using Parser 3.3.5.0, rubocop-ast 1.32.3, running on ruby 3.3.5) [x86_64-linux] - rubocop-minitest 0.36.0 - rubocop-performance 1.21.1
The text was updated successfully, but these errors were encountered:
fix rubocop#321
1da48c7
[Fix rubocop#321] check for assertion method receiver
e6e08a6
No branches or pull requests
All methods which start with "assert_" or "refute_" are currently assumed to be (and counted as) Minitest assertions. E.g.
With
Minitest/MultipleAssertions
Max of 1 the following registers an offense.Expected behavior
No offense should be registered, as only one Minitest assertion is called in the test.
Actual behavior
Offense is registered.
Steps to reproduce the problem
See above code sample
RuboCop version
The text was updated successfully, but these errors were encountered: