Fix TestTask verbose

[mblumtritt]

rake test —verbose did not result in verbose mode for MiniTest.

The verbose option needs to be forwarded to the Ruby call.

Missing tests are added.

[mblumtritt]

Seems that TestRakeApplicationOptions#test_missing_require is broken in Ruby:ruby-head but not with this pull request. Can somebody help out, please?

[MarkDBlackwell]

rake test --verbose did not result in verbose mode for MiniTest. The verbose option needs to be forwarded to the Ruby call.

Minitest sometimes emits the message: "You have skipped tests. Run with --verbose for details."

Likely, this message stimulated the above suggestion.

This comment by @shunsuke227ono explains what's really happening—as well as this one by @prathamesh-sonpatki.

Generally, this problem only arises when three independent, particular bodies of software—Rake::TestTask, Minitest, and user test code—are combined. In that case, the proper message should suggest TESTOPTS="--verbose" (rather than --verbose).

Perhaps Rake::TestTask should detect use of Minitest, then ensure the correct message is emitted (whenever tests are skipped) by subclassing Minitest's SummaryReporter to override method summary as Minitest recommends here. Then Rake::TestTask should swap its new class into this list.

Rake's own test suite uses Minitest. When tests are skipped, it displays the problem: Minitest emits the above, incorrect message.