Unit tests for LicenseCheckTask. [LUCENE-5210]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
While working on #6273, I noticed the LicenseCheckTask is kind of a second class citizen - excluded from UI src folder setup and with no units tests. This was a little scary to me.
I've started adding some units tests. So far I have mainly just done the lifting of getting units tests to work as part of tools.
I have added two super simple tests - really just the start - but something to build on.
---
Migrated from [LUCENE-5210](https://issues.apache.org/jira/browse/LUCENE-5210) by Mark Miller (@markrmiller), updated Sep 16 2013
Attachments: [LUCENE-5210.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-5210/LUCENE-5210.patch) (versions: 2)
Contributor guide
Research direction
Start by reviewing LicenseCheckTask and the two existing unit tests described in the issue, along with the attached LUCENE-5210.patch. Run the relevant tools tests first, then extend coverage beyond the initial cases until the task has meaningful unit-test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100