opensearch-project / opensearch-project/opensearch-java
[PROPOSAL] migrate to JUnit 5
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 165
- Forks
- 250
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 26
Description
What/Why
What are you proposing?
the project should (eventually) migrate to JUnit 5 so that the newer features & patterns can be used and so that it isn't stuck on an old major release of JUnit.
What users have asked for this feature?
n/a
What problems are you trying to solve?
avoid getting stuck on an old library.
What is the developer experience going to be?
- no changes for users of opensearch-java
- more modern experience for developers of opensearch-java
Are there any security considerations?
no
Are there any breaking changes to the API
no (only affects the tests)
What is the user experience going to be?
n/a
Are there breaking changes to the User Experience?
no
Why should it be built? Any reason not to?
long-term stability by being on the current major release of the testing library and improved developer experience
What will it take to execute?
manual effort to migrate it (maybe part of it can be automated?).
Any remaining open questions?
n/a
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The proposal names no files, test classes, or build entry points. Start by inspecting the project's test configuration and inventorying its JUnit usage; done means the test suite runs on JUnit 5 without user-facing API changes.
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
- 25/100