You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 10, 2022. It is now read-only.
Initially tests in jtransc were designed with practicality in mind. Instead of unittest everything I work on case-use tests; in this case integration tests. That make tests less fragile and it is easier to change a design without breaking tests. Jacoco works at per-module. It just tests again classes in its own module by default. That mean that integration tests between projects doesn't measure coverage in other modules.
We have two options here:
Do proper unittests at each module, and just consider unittesting for coverage
Tell jacoco to measure coverage in classes of other projects, since codecov is going to merge coverage reports
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Initially tests in jtransc were designed with practicality in mind. Instead of unittest everything I work on case-use tests; in this case integration tests. That make tests less fragile and it is easier to change a design without breaking tests. Jacoco works at per-module. It just tests again classes in its own module by default. That mean that integration tests between projects doesn't measure coverage in other modules.
We have two options here:
The text was updated successfully, but these errors were encountered: