Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-10635

Ensure test coverage for WANDScorer after additional scorers get added

Details

    • Test
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None
    • New

    Description

      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?

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              zacharymorn Zach Chen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 50m
                  50m