I don't see the test, so hard for me to tell for sure... but there are
lots of scaffolding around this class as I inserted an empty test
containing an assumption and it initializes lots of stuff; the
assumption has to be triggering there somewhere.
Once your test fails or assume-fails, locate:
I traced the issue to a specific change that was made to the
StreamExpressionTest. I'm figuring out the best way to address the issue.
Joel Bernstein
http://joelsolr.blogspot.com/
On Tue, Feb 21, 2017 at 2:52 PM, Joel Bernstein wrote:
> Hi Dawid,
>
> It does appear to be
Hi Dawid,
It does appear to be related to an assumption. I researching what the issue
is. Also I was using -Dtestmethod to specify the method which does not seem
to be correct. I have a reproduce method that looks like this:
NOTE: reproduce with: ant test -Dtestcase=StreamExpressionTest
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
Hi Steve,
It's misspelled the same way in the method and the command line. I'll fix
the misspelling, but something else is going on here that is causing the
test to be ignored.
Joel Bernstein
http://joelsolr.blogspot.com/
On Tue, Feb 21, 2017 at 1:51 PM, Steve Rowe wrote:
>
Hi Joel,
Looks like testSignifcantTermsStream is misspelled? (missing “i” between “f”
and “c”)
—-
Steve
www.lucidworks.com
> On Feb 21, 2017, at 1:23 PM, Joel Bernstein wrote:
>
>
> A test I've just added is being ignored when it's being called with the
> -Dtestmethod.