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

Improve unit test coverage #791

Open
rgwozdz opened this issue Sep 14, 2023 · 0 comments
Open

Improve unit test coverage #791

rgwozdz opened this issue Sep 14, 2023 · 0 comments
Labels
Good first issue Good for newcomers / first-timers internal Changes only affect the internal API LOE: low Level Of Effort: low

Comments

@rgwozdz
Copy link
Member

rgwozdz commented Sep 14, 2023

Each monorepo package has some degree of test coverage. Note that some packages include "integration" tests as well as specific unit tests. This is a legacy of early development on these packages, where initial tests were geared towards specific feature functionality (e.g., filtering) rather than specific function input/output. Over time, we have moved towards a unit approach on individual packages, and are now moving integration tests to the root level of the monorepo.

Ideally, we want to achieve 100% unit test coverage on all packages. You can test unit coverage specifically with:

npm run test:cov:unit

Then review the coverage report at:

coverage_unit/index.html

This report will reveal where tests could and should be added.

@rgwozdz rgwozdz added internal Changes only affect the internal API Good first issue Good for newcomers / first-timers LOE: low Level Of Effort: low labels Sep 14, 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 / first-timers internal Changes only affect the internal API LOE: low Level Of Effort: low
Projects
None yet
Development

No branches or pull requests

1 participant