Joel, your test is being executed, but there is some kind of assumption that is thrown within the body of the method (or in setup/ teardown) that is causing the test to be ignored. Assumptions are regular exceptions -- try wrapping in try/catch and dumping the stack trace if you can't locate it easily. Alternatively, I think the test execution dumps may carry a full stack already?
Dawid On Tue, Feb 21, 2017 at 7:23 PM, Joel Bernstein <joels...@gmail.com> wrote: > > A test I've just added is being ignored when it's being called with the > -Dtestmethod. > > Here is the command line: > > ant test -Dtestcase=StreamExpressionTest > -Dtestmethod=testSignifcantTermsStream > > > Here are some snippets from the output: > ------------------------------ > ------------------------------ > > [junit4] 2> 6440 INFO > (TEST-StreamExpressionTest.testSignifcantTermsStream-seed#[619661D6DA496076]) > [ ] o.a.s.SolrTestCaseJ4 ###Ending testSignifcantTermsStream > > [junit4] IGNOR/A 0.18s | StreamExpressionTest.testSignifcantTermsStream > > [junit4] > Assumption #1: got: <false>, expected: is <true> > > .... > > [junit4] Tests summary: 1 suite, 1 test, 1 ignored (1 assumption) > > ------------------------------------- > > ------------------------------------- > > Is anyone else seeing this behavior or have any idea why this might be > happening? > > > > Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
