In sbt 1.0.x, running scripted with an argument that selects no tests will blissfully succeed. For example:

> scripted abc/xyz

About to run tests: 
 * abc/xyz

[success] Total time: 21 s, completed Nov 16, 2017 7:03:50 PM

even though there is no such test. That may lead developers to errors if they inadvertently mistype the name of their tests, in scripts or elsewhere.
Instead, if an argument is supplied to scripted, and no tests are matching, scripted should fail, or at least warn the user, rather than making it appear that it is successfully running a non-existing test. Replacing "About to run tests [...]" with "Tests selected: [...]", and then printing "No tests found" in place of "Running..." if no tests are run would suffice.