Skip to content

Conversation

@evgeni
Copy link
Member

@evgeni evgeni commented Jan 5, 2026

No description provided.

Gemfile Outdated
Comment on lines 13 to 15
if RUBY_VERSION >= '3.2'
gem 'minitest-mock' # minitest-mock was removed from minitest 6.0 which is Ruby 3.2+
end
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is ugly and I think it's easier to pin minitest to ~> 5.0 for now

Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 for pinning to minitest 5 for now.


it 'has no config file' do
_(subject.config_file).must_equal(nil)
_(subject.config_file).must_be_nil
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've been leaning to using the assert_* statements more because IMHO they're easier to read. So instead go with:

Suggested change
_(subject.config_file).must_be_nil
assert_nil subject.config_file

But that's rather inconsistent with the rest of the file

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's why I didn't change it like this :)

- 6.x splits out Minitest::Mock into an own gem: minitest-mock
- 6.x requires Ruby 3.2
- minitest-mock requires Ruby 3.1

As we need to keep Ruby 3.0 compatibility, we can't depend on
minitest-mock unconditionally.

Let's keep us on minitest 5.x for now
@evgeni
Copy link
Member Author

evgeni commented Jan 5, 2026

Technically we can skip changing the nil tests now that we pinned to 5.x (it's only a problem for 6.x), but it was the only failure that actually made things fail on 6.x besides the mock thing, so I felt like it's a good addition anyway.

@ekohl ekohl merged commit 416a170 into master Jan 5, 2026
8 checks passed
@ekohl ekohl deleted the fix-tests branch January 5, 2026 12:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants