LuceneTestCase exposes too much innards as public [LUCENE-4244]
Open
legacy-jira-priority:Major
type:task
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
This can be confusing if you are trying to write a test. We should try to clean up the visibility
---
Migrated from [LUCENE-4244](https://issues.apache.org/jira/browse/LUCENE-4244) by Robert Muir (@rmuir)
Attachments: [LUCENE-4244.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-4244/LUCENE-4244.patch)
Contributor guide
Research direction
Start by reviewing LuceneTestCase and the attached LUCENE-4244.patch to identify which public members are considered unnecessary. Determine the visibility changes that reduce confusion for test authors, then verify that the affected tests still work and that only intended APIs are changed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100