I thought about doing this. I agree that it doesn't necessarily hurt to have it duplicated here too. My reasoning for not taking that route was:

- this isn't coincidental duplication; we're duplicating these lines solely because minitest is being loaded
- we don't always load minitest, so why have the extra API surface area
- if more dependencies are required by minitest in the future we need to make sure to add them in two places; I know I personally would forget to add it to 'test_unit' if that were to happen
- the code in this manner is fairly self documenting, I'd feel odd duplicating the comments about the minitest issue again here
- I considered making a `minitest_assertions_hooks` module, which I could include in both; though part of me though this was slightly better documenting

With all that having been said. Neither of these modules have specs around them. I probably easily could just use a `shared_examples_for "provides minitest hooks"` to help add the documentation.

Honestly, I'm on the fence about my approach and figured I'd make sure it passed on all versions and then solicit feedback.