'ceylon test my.module' could test 'test.my.module' if 'my.module' isn’t a test module

[CeylonMigrationBot]

[@lucaswerkmeister] The conventional name for my.module’s test module is test.my.module, which means that (unless you’re using e. g. ant) you’ll typically test with ceylon test test.my.module. That double test feels redundant; perhaps ceylon test my.module could prepend test. automatically if my.module isn’t a test module (doesn’t shared import ceylon.test)?

(Feature request, not for 1.1.)

[Migrated from ceylon/ceylon-runtime#70]

[CeylonMigrationBot]

[@quintesse] Is certainly an option, although maybe I'd go for:

1. if the name does not start with test. add that and try it
2. if it doesn't exist try the original name

Maybe that way we can better "promote" the use of the name test.* for test modules. (if that's what we want of course)

[CeylonMigrationBot]

[@lucaswerkmeister] That would mean that if test.my.module exists, I can never ever test my.module. I can’t really imagine why I would want to do that, but still, it sounds a tad scary to me. (Perhaps I’d want to have some small temporary test, and would put that into my.module so I can run it individually, or so it has access to unshared members? Dunno.)

[CeylonMigrationBot]

[@quintesse] Hmm true.
Thing is I don't like it too much when code changes might suddenly change the way existing scripts might run. You add import ceylon.test and suddenly some kind of test script you didn't even know about starts to fail.
You might have to tell people to never use these "user friendly tricks" in scripts.

[CeylonMigrationBot]

[@lucaswerkmeister] Good point, that would make this feature kind of useless.