Use JUnit4 capabilites for more thorough Locale testing for classes deriving from LocalizedTestCase [LUCENE-2122]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Use the `@Parameterized` capabilities of Junit4 to allow more extensive testing of Locales.
---
Migrated from [LUCENE-2122](https://issues.apache.org/jira/browse/LUCENE-2122) by Erick Erickson (@ErickErickson), updated May 09 2016
Attachments: [LUCENE-2122.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-2122/LUCENE-2122.patch) (versions: 2), [LUCENE-2122-r2.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-2122/LUCENE-2122-r2.patch), [LUCENE-2122-r3.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-2122/LUCENE-2122-r3.patch), [LUCENE-2122-r4.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-2122/LUCENE-2122-r4.patch)
Contributor guide
Research direction
Start by reviewing the LUCENE-2122 attachment revisions and locating Lucene test classes deriving from LocalizedTestCase. Check how JUnit4 @Parameterized is used in the existing test suite, then run the affected locale tests. Done means those tests exercise a broader set of Locales under parameterization without losing existing coverage.
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
- Mostly clear
- Newbie friendliness
- 35/100