You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Zach Chen (Jira)" <ji...@apache.org> on 2022/07/01 03:25:00 UTC

[jira] [Created] (LUCENE-10635) Ensure test coverage for WANDScorer after additional scorers get added

Zach Chen created LUCENE-10635:
----------------------------------

             Summary: Ensure test coverage for WANDScorer after additional scorers get added
                 Key: LUCENE-10635
                 URL: https://issues.apache.org/jira/browse/LUCENE-10635
             Project: Lucene - Core
          Issue Type: Test
            Reporter: Zach Chen


This is a follow-up issue from discussions [https://github.com/apache/lucene/pull/972#issuecomment-1170684358] & [https://github.com/apache/lucene/pull/972#pullrequestreview-1024377641] .

 

As additional scorers such as BlockMaxMaxscoreScorer get added, some tests in TestWANDScorer that used to test WANDScorer now test BlockMaxMaxscoreScorer instead, reducing test coverage for WANDScorer. We would like to see how we can ensure TestWANDScorer reliably tests WANDScorer, perhaps by initiating the scorer directly inside the tests?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org