Copy/Move critical pieces of Monster tests into continuous integration [LUCENE-6008]
Open
affects-version:5.0
affects-version:6.0
legacy-jira-fix-version:5.0
legacy-jira-fix-version:6.0
legacy-jira-priority:Major
type:test
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
@rmuir mentioned on #7064 that some of the things in `@Monster` tests might be important enough to move into tests that are run by continuous integration (Jenkins).
---
Migrated from [LUCENE-6008](https://issues.apache.org/jira/browse/LUCENE-6008) by Shawn Heisey (@elyograg), updated May 09 2016
Contributor guide
Research direction
Start by reading the @Monster tests and the discussion in issue #7064 or LUCENE-6008 to identify which checks are considered important. Then inspect the Jenkins continuous-integration setup and determine which tests should move there; done means the selected critical coverage runs reliably in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100