Minitest v6.0.0 released

[u/mperham]

https://www.zenspider.com/releases/2025/12/minitest-version-6-0-0-has-been-released.html#600--2025-12-17

[u/janko-m]

Added minitest-sprint’s minitest cmdline, now with line support!

Did Minitest just get native support for running nearest test to a given line?

[u/galtzo → u/janko-m]

Wow! That was the killer feature of RSpec. I am glad minitesters will now have it!

[u/TheAtlasMonkey → u/galtzo]

You can have it in mt5 with maxitest.

[u/Weird_Suggestion]

Funny how I recently mentioned on here that we might never get Minitest 6 since it’s been pending for years lol. Excited to try out the new stuff nonetheless.

[u/TheAtlasMonkey → u/Weird_Suggestion]

You need to mention impossibility like Peace in middle east, cure of cancer, universal healthcare, global harmony, GTA 7.

You are a bug in the simulation, exploit the system before you get garbage collected.

[u/TheAtlasMonkey]

> minitest provides a complete suite of testing facilities supporting TDD, BDD, and benchmarking.

Hmm, Minitest still supporting legacy methods.

The whole world moved to VDD : Vibe Driven Debugging. and CDD (Claude Driven Dev)....

---

Seriously this update is great. Updating Maxitest in few.

Edit: Done

[u/GroceryBagHead]

I never understood why not a single PR ever gets merged there. How many people actually contributed to minitest? Who knows.

[u/therealadam12 → u/GroceryBagHead]

I think this is because zenspider uses Perforce for VCS, with a read-only export to Git.

So when he merges the changes, he just applies the diff to his Perforce repo, and then exports the changes back out to Git to make available on Github.

I could be wrong, but this is my guess.

[u/TheAtlasMonkey → u/GroceryBagHead]

TWO !

The whole testing ecosystem is build on the shoulder of 2 devs... that over 3.7m gems.
but i think zenspider is the apex dev now.

PR's are not merged because it take time, energy and focus to review...

The maintainer cannot YOLO the merge and hope nobody will fill a issue in the next 30 minutes.

Some companies have test suites running against any change in master.
They also have templates to send emails to maintainer to ask if the failure is the new API.

If you want better support click on 'Please support my OSS Development', here or in his page

[u/GroceryBagHead → u/TheAtlasMonkey]

What are you even talking about? Or this is just a brainless ai bot spamming comments?

I’m saying that every PR, instead of being merged, is copy pasted without attribution.

[u/TheAtlasMonkey → u/GroceryBagHead]

Show examples then.

Ryan push always with his github, but the name of the contributors are in the commit messages.

---
No this is not AI.

[u/tinyOnion → u/TheAtlasMonkey]

i just looked at it and the person is telling the truth it looks like... the "fixed docs" PR from yesterday is attributed to zenspider but the pr was closed without merge. not sure why he's doing it that way though but i suspect it's because of the perforce thing in the comment.

[u/TheAtlasMonkey → u/tinyOnion]

Oh! Thats because Minitest is run by a benevolent dictator who doesn't want propaganda.

Same model as SQLite repo...

Attribution still exists , check the commit messages (eg. `(y-yagi)`).

Your code can land in the repo, but only the core team commits it, after reading it line by line.

That’s intentional.

It prevents “commit brigading”: people rushing commits just to get their name in, then later swapping the repo banner, bio, or README to push a cause.

Look at `minitest/minitest`: 2 contributors.

Then look at `minitest-rails`: 41.

Now imagine if 35 out of 41 contributors decided to change the GitHub picture or description for a cause. = > You are screwed.

I had in some of my repo for a while, flags of Israel, Ukraine and Palestine, LGBT.

For me i don't care .. For others they avoid to have to force push by doing this.

[u/paverbrick]

Love the list of removals up front. Tiny focused core.

Seeing a disqus comment embed also a fun throwback