Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Standardize, setup, report, and increase test coverage #298

Closed
Tracked by #30
Xtansia opened this issue Sep 14, 2022 · 5 comments
Closed
Tracked by #30

[FEATURE] Standardize, setup, report, and increase test coverage #298

Xtansia opened this issue Sep 14, 2022 · 5 comments
Labels
good first issue Good for newcomers

Comments

@Xtansia
Copy link
Contributor

Xtansia commented Sep 14, 2022

Setup code coverage, once reporting from CI/CD analyze the test gap and fill it.

See the meta issue opensearch-project/opensearch-clients#30 for details.

@DiyazY
Copy link

DiyazY commented Mar 27, 2023

Hi. I can look at this. Is it ok if we close this issue with several PRs?
For example: 1st PR is setting up the test coverage, 2nd or Nth PRs are about increasing the test coverage. I think it will make the review process much easier.

Do we have any preferred test coverage tool? I assume it is codecov.

Tag: CCI

@dblock
Copy link
Member

dblock commented Mar 27, 2023

No preference on coverage tool.

@DiyazY
Copy link

DiyazY commented Mar 28, 2023

@dblock Thank you! I will take this issue.

@tejeshreddy
Copy link
Contributor

tejeshreddy commented Dec 6, 2023

@dblock could you please provide more information on this issue? The current code coverage is 96% for this repo, does this issue expect to fill the gaps where the tests aren't covered?

@dblock
Copy link
Member

dblock commented Dec 6, 2023

Looks like this was done, closing.

@dblock dblock closed this as completed Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

5 participants