I'm with Luke in this case regarding the separator character. Two of the benefits of '#':
- Test method calls and test classes are easily distinguishable by looking at them. - Using "." will leave the user wonder: "How does it know I'm referring to a method?" which could be a source of misunderstanding. By the way, using "::" instead of "#" would be consistent with Java 8 notation (not that it is really that important). To me however, it is more important that I can start the test method from the command line and a clear (unambigous) syntax would be better here. I believe why it is mostly needed is to (re)test a single method when something is broken (and is assumed to be fixed) which is not a predefined set of test methods. Although probably there are good cases for the predefined set of methods (to group quicker tests, etc.). -- View this message in context: http://gradle.1045684.n5.nabble.com/supporting-the-execution-of-a-particular-test-method-tp5711996p5712039.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
