sbt testOnly command should fail/warn when no test found

problem

if you do a typo on the sbt testOnly command you will hardly notice the test you were expecting didn’t run.

Current output:

(...)
[info] Run completed in 46 milliseconds.
[info] Total number of tests run: 0
[info] Suites: completed 0, aborted 0
[info] Tests: succeeded 0, failed 0, canceled 0, ignored 0, pending 0
[info] No tests were executed.
[info] No tests to run for test:testOnly
[success] Total time: 69 s, completed May 11, 2017 10:36:33 AM

notice the last line, which says success. If you do a quick read, you probably won’t notice. At least myself, I just look for the green or red line at the bottom to see if everything it’s ok.

expectation

Why not fail? Or at least something more noticeable?

notes

Available to contribute, just need some guidelines

[pedrorijo91]

I would love to contribute. You can assign this to me. I hadn’t a lot of free time to dig into sbt recently, but I think better days are coming 😃 (I already cloned and ran the tests, it’s a good start 😛)

[eed3si9n]

If the root project aggregated subprojects projA, projB, and projC, and you type in testOnly a.foo, would you fail the whole operation because a.foo doesn’t exist on projB?