I think there's more we could do in this area, but this implements
@dchelimsky's suggestion whic...

All expectations defined within the block are constrained by the
sequence.

For example, the fol...

We updated the code to use Ruby v1.9 Hash syntax in #598. This brings
the docs into line with th...

Tidy up Minitest vs MiniTest references

As noted by @zenspider in this comment [1], the rename is over 10 years
old, so it seems about t...

All of these are either references to constants internal to Mocha or
documentation referencing t...

As per this comment [1]. Thanks, @Maimer!

As of Minitest v5.19.0 [2], there's no need to requir...

We've had `Mocha::Detection::MiniTest.version` for some time and it does
a more thorough job tha...

This provides a terser syntax for matching an object which responds in a
certain way, e.g.

...

It turns out that YARD displays a special section "Dynamic Method
Handling" for classes that imp...

It turns out we were relying on the very old [1] MiniTest module name
rather than the newer Mini...

I never look at the data from this and in any case I don't ask
permission to track people on the...

This reverts commit 12f1eef7dbe7cd65104327b6a958cf3b8f50989a.

The problem I reported in lsegal/...

I'm not sure why/when this token became invalid, but I suspect it was a
while back when there we...

This reverts commit b8e6d064b8b9bfeb37d6534bbb4e37856dfec5b7.

The problem identified in #591 wa...

It seems as if the recent v0.9.29 release of yard broke my custom
template code. I plan to repor...

It seems as if recent versions of minitest now require a more recent
version of Ruby. Without th...

Ruby v3.2.0 was recently released [1].

[1]: https://www.ruby-lang.org/en/news/2022/12/25/ruby-3...

Mocha >= v2 only supports Ruby >= v2 and so this check is redundant in
the main branch.

Since support for Ruby 1.8 has been dropped.

Currently 4 tests are failing in JRuby v9.4.0.0, e.g. this build [1].

This is due to a JRuby is...

This has only ever supported `debug`, `verbose` & `skip_integration`
options. However, it curren...

Fixes #537

We do regular testing of ruby-head, so our gem paths include a `+`
which has a special meaning i...

Object#~= has been removed from Ruby v3.2 [1].

Closes #590.

[1]: https://bugs.ruby-lang.org/is...

In preparation for the release of Ruby v3.2.

The regression was inadvertently introduced in this commit [1] and
indirectly led to this issue ...

And so should be included as such in the gemspec; not in the Gemfile.

I've specified the '>= 0....

Note that the release notes from the v2.0.0.alpha & v2.0.0.alpha.1
pre-releases have been combin...

Closes #577.

This addresses an ambiguity which was raised in this comment [1].

Since it's a bit subjective w...

While strictly speaking the commits relating to these changes [1,2]
didn't make it into v2 relea...

By including the source location of the stub definition.

This change is a necessarily a bit per...

This is useful when using `ExecutionPoint.current` to make tests more
robust.

* Make them more consistent with the docs for Expectation#with.
* Mention & explain deprecation ...

This converts the deprecation warning introduced in
d66c2b501685fe827a2c5e2236475e78d8082c11 int...

The following methods were deprecated in #421 and released in v1.10.0:

* Configuration.allow
* ...

In Mocha v1.10.0 some undocumented behaviour changed without any prior
deprecation warning.

* T...

This removes Configuration#reinstate_undocumented_behaviour_from_v1_9
and its setter. The behavi...

This removes the optional deprecated behaviour in Expectation#yields &
Expectation#multiple_yiel...

This removes the optional deprecated behaviour in API#mock, API#stub &
API#stub_everything which...

I'm not sure these calls to DeprecationDisabler.disable_deprecations
were ever necessary. Curren...

This was missed in 472d54161fab9bbd093a8b8c6928a423cbad9897.

Previously this was the recommended way to integrate Mocha with a test
framework. However, this ...

If someone is explicitly requiring "mocha/test_unit" or "mocha/minitest"
then the implication is...

Versions of minitest earlier than v3.3.0 are no longer supported.

Closes #541.

Use the value returned by Detection::TestUnit.testcase as the target of
the TestUnit::Adapter mo...

Gem versions of test-unit earlier than v2.5.1 and versions of test-unit
from the Ruby v1.8 stand...

This will generate a deprecation warning if Ruby >= v2.7,
Configuration#strict_keyword_argument_...

When strict_keyword_argument_matching configuration option is not set.

Closes #562.

This introduces a new `strict_keyword_argument_matching` configuration
option. Thi...

With the introduction of strict keyword matching, we're explicitly
distinguishing between positi...

Previously in the description of an invocation or of a parameter
matcher, a single Hash argument...

When the strict keyword argument option is enabled, an expectation
expecting keyword arguments (...

This marks Expectation#with, Mock#method_missing, and the method defined
by StubbedMethod#define...

This option doesn't currently do anything, but in a subsequent commit it
will determine whether ...

We're planning to change how this works once we're explicitly
distinguishing between keyword and...

This is to better characterize the existing behaviour. It should also
make it clearer what chang...

Make more of a distinction between test failures and errors. Explicitly
assert for what we are e...

This was introduced in this commit [1] apparently as a precursor to the
addition of ParameterMat...

I think this makes the code more readable.

Closes #552.