opensearch-project / opensearch-project/reporting
[Testing Confirmation] Confirm current testing requirements
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 35
- Forks
- 87
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 7
Description
As part of the discussion around implementing an organization-wide testing policy, I am visiting each repo to see what tests they currently perform. I am conducting this work on GitHub so that it is easy to reference.
Looking at the Reporting repository, it appears there is
| Repository | Unit Tests | Integration Tests | Backwards Compatibility Tests | Additional Tests | Link |
|---|---|---|---|---|---|
| Reporting | Link checker, Certificate of Origin | https://github.com/opensearch-project/reporting/issues/653 |
I don't see any requirements for code coverage in the testing documentation. If there are any specific requirements could you respond to this issue to let me know?
If there are any tests I missed or anything you think all repositories in OpenSearch should have for testing please respond to this issue with details.
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 by reviewing the Reporting repository's current testing documentation and the tests referenced by the issue. Done means confirming whether code-coverage or other testing requirements exist and recording any missing requirements, but the issue names no files or test paths.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100