opensearch-project / opensearch-project/security-analytics
Add backwards compatibility tests for automation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 111
- Forks
- 111
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 13
Description
Add backwards compatibility tests for the plugin to automate end-to-end upgrade paths for faster releases.
Developer documentation for implementing bwc tests and hooking them to CI: https://github.com/opensearch-project/opensearch-plugins/blob/main/TESTING.md#backwards-compatibility-testing
This would include the BWC tests on both plugin level and distribution bundle level.
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
Start with the backwards-compatibility testing guidance in TESTING.md, then determine the plugin-level and distribution-bundle-level upgrade paths described in the issue. Done means end-to-end BWC tests cover both levels and are hooked into CI for automated release validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100