Minitest::EmptyLineBeforeAssertionMethods errors on assertions with block arguments

[petergoldstein]

Minitest::EmptyLineBeforeAssertionMethods does not properly handle assertions that are invoked with a block argument. Passing a block argument results in an error - undefined method args_type?' for ...`

---

Expected behavior

RuboCop Minitest should treat an assertion with a block argument identically to one where the block is explicitly specified.

Actual behavior

RuboCop Minitest generates an error when it processes this line

An error occurred while Minitest/EmptyLineBeforeAssertionMethods cop was inspecting ...
undefined method args_type?' for ...`

Steps to reproduce the problem

Consider the example from Minitest::Assertions#assert_raises

error = assert_raises(CustomError) do
  raise CustomError, 'This is really bad'
end

assert_equal 'This is really bad', error.message

A file with this code is parsed without error by RuboCop Minitest. But if we alter this code slightly to read:

blk = ~> { raise CustomError, 'This is really bad' }
error = assert_raises(CustomError, &blk)

assert_equal 'This is really bad', error.message

then RuboCop Minitest generates an error undefined method args_type?' for ...`

RuboCop version

Include the output of rubocop -V or bundle exec rubocop -V if using Bundler. Here's an example:
You see extension cop versions (e.g. rubocop-minitest, rubocop-performance, and others) output by rubocop -V,
include them as well. Here's an example:

$ [bundle exec] rubocop -V
1.37.1 (using Parser 3.1.2.1, rubocop-ast 1.23.0, running on ruby 3.0.4) [x86_64-darwin21]
  - rubocop-minitest 0.23.0
  - rubocop-performance 1.15.0
  - rubocop-rake 0.6.0