On Tue, Oct 15, 2013 at 6:56 AM, Dawid Weiss <dawid.we...@cs.put.poznan.pl> wrote: >> Hmm, you couldn't just enter the unqualified class name, and then it'd >> match any package containing that class name? LIke "**/TestFooBar" >> patternset pattern I think? > > This isn't different to your "duplicated test match" scenario. Same > class could be present in multiple packages -- what then? :)
Just run both tests in that case, I think? User can fully qualify if they really want to run a specific one? That's a much more benign error than saying BUILD SUCCESSFUL when no test actually ran. >> Hmm, so globs are a convenient way to work around a JUnit limitation? > > I'm not talking about globs, I'm talking about the fact that every > test needs a unique string description so if you want to re-run the > same method multiple times in JUnit you need to differentiate them > somehow. Then when you want to rerun your test and limit to that > particular method you need to glob somehow because these descriptions > no longer correspond to raw method names... eh, it's a longer > discussion. OK, hairy :) >> I also did not remember -Dtests.method=XXX was different.... I believe >> you've explained this many times already ;) >> >> I'll [hopefully remember to] use -Dtests.method from now on! > > See the top of 'ant test-help': Thanks. > You're right -- testmethod is a prefix match and testcase is a suffix/ > class match. The runner only "understands" tests.class and > tests.method -- if you're running from Eclipse or Idea, for example, > only these will be picked up. OK. Mike McCandless http://blog.mikemccandless.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
