You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2015/04/12 20:31:12 UTC
[jira] [Resolved] (LUCENE-6411) Add AssertingSpans
[ https://issues.apache.org/jira/browse/LUCENE-6411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir resolved LUCENE-6411.
---------------------------------
Resolution: Fixed
Fix Version/s: 5.2
Trunk
I added an initial AssertingSpanQuery and tied it into span search equivalence tests. It makes it easy to find bugs in two-phase iteration and stuff like that (necessary to really debug them at all).
Maybe we can improve it and use it in other places, but for now its a start.
> Add AssertingSpans
> ------------------
>
> Key: LUCENE-6411
> URL: https://issues.apache.org/jira/browse/LUCENE-6411
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Fix For: Trunk, 5.2
>
>
> Currently Spans needed a lot of asserts in every Spans to make it possibly to debug things. If you miss a single assert, bugs are hidden or not narrowed down the problematic Spans class.
> Instead I think it would be better if we made a test-framework/AssertingSpansQuery that wrapped another SpanQuery and added all the checks. We could use it to really improve the debuggability and coverage of tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org