NoMethodError: undefined method 'stubs'; alternative to nesting with `stub` about minitest HOT 2 CLOSED

Minitest has never had a plural stubs method. Nor has it ever had a returns method. So upgrading must have gotten rid of some dependency you were using.

Minitest documentation is here: https://docs.seattlerb.org/minitest/README_rdoc.html#label-Stubs which says:

Minitest’s stub method overrides a single method for the duration of the block.

and is kinda the whole point. If you need to stub that much out of the gate to test something, that should be considered a smell. You're probably testing at the wrong level or your code isn't designed to be easily testable.

from minitest.

As this is an integration test, I am not convinced that it's a code smell, since there are a bunch of external services that need to be stubbed.

As for the Minitest docs, I'm not sure if there's more to the docs regarding stubs - the only thing I see is a single statement and example, which suggests that the only way to stub is indeed with a block.

  # Minitest’s stub method overrides a single method for the duration of the block

  Time.stub :now, Time.at(0) do   # stub goes away once the block is done
    assert obj_under_test.stale?
  end

I appreciate your response nonetheless, as you saying "upgrading must have gotten rid of some dependency you were using" got me thinking, and I realized that no, upgrading did not do that. I looked harder, and ended up figuring out what the plural stubs is - it's Mocha's stubs. I realize that I misled you by saying that "I upgraded and now there's an error" - and I am sorry for that (in retrospect, I didn't realize exactly what was happening).

The problem was that when I was running this single test on its own, it was failing with undefined method 'stubs' because there was no require 'mocha/minitest' in that file (I guess the test wasn't failing when the entire test suite was run because mocha/minitest was require'd elsewhere in the test suite). Anyway, I added require 'mocha/minitest' and now the test is passing when run on its own, and it looks much nicer than the nested way:

Users::ContactBuilderJob.stubs(:call).returns(true)
AnotherModel::JobOne.stubs(:call).returns(true)
AnotherModel::JobTwo.stubs(:call).returns(true)
AnotherModel::JobThree.stubs(:call).returns(true)
# assertions

Note that until I figured this out I had temporarily used the nested stubbing way of native Minitest, and indeed it worked just the same. The only difference is aesthetic.

I appreciate that stub goes away once the block is done. This is a noteworthy feature.

from minitest.