Skip to content
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.

add coverage to the test #39

Open
piyusql opened this issue Oct 6, 2023 · 0 comments
Open

add coverage to the test #39

piyusql opened this issue Oct 6, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@piyusql
Copy link
Contributor

piyusql commented Oct 6, 2023

Is your feature request related to a problem? Please describe.

currently we do unit tests for each module, we should add coverage such that we will be knowing that how much code has been covered by the test cases.
it will eventually improve our code quality and eventually it will avoid any regressions in long run.

Describe the solution you'd like

coverage is a good library to be used

Describe alternatives you've considered

No response

Additional context

No response

@piyusql piyusql added the enhancement New feature or request label Oct 6, 2023
@piyusql piyusql added this to the v0.2.4 milestone Oct 6, 2023
@piyusql piyusql self-assigned this Oct 6, 2023
piyusql added a commit that referenced this issue Oct 6, 2023
coverage library has been used to gauge unittest coverage
current test coverage for bridgeql code is 87%
you can just check it with 'make test' command with every change
ref #39

Signed-off-by: Piyus Kumar <piyusk@vmware.com>
piyusql added a commit that referenced this issue Oct 6, 2023
coverage library has been used to gauge unittest coverage
current test coverage for bridgeql code is 87%
you can just check it with 'make test' command with every change
ref #39

Signed-off-by: Piyus Kumar <piyusk@vmware.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant