Minitest has a number of cheeky little judgments like this [1][2], especially in the docs. That said they support all these things they don't prefer, within rea

Minitest has a number of cheeky little judgments like this [1][2], especially in the docs. That said they support all these things they don't prefer, within reason, and I appreciate that. Minitest is also full of all sorts of weird peccadillos like being written in the "Seattle.rb style" and autloading files in all gems that match a certain path [3]. These are not how I'd structure a plugin framework or write code, but it works and the code is easy to understand and hack on. I've spent a lot of time reading the internals of minitest, monkey patching or generally torturing it in ways they probably wouldn't prefer and it's been a trustworthy, if a little bit judge-y, tool for years. [1] https://github.com/minitest/minitest/blob/master/lib/minitest/spec.rb#L245 https://github.com/minitest/minitest/blob/master/lib/minites... [2] https://github.com/minitest/minitest/blob/master/lib/minitest/spec.rb#L214-L216 https://github.com/minitest/minitest/blob/master/lib/minites... [3] https://github.com/minitest/minitest/blob/master/lib/minitest.rb#L112 https://github.com/minitest/minitest/blob/master/lib/minites...