-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Question: Is there a unit test coverage metric for vitess? #14326
Comments
We don't have any automated coverage report setup on the repo ATM that I'm aware of. We did at one point but I believe it had stopped working and thus we removed it: 3e9f4c7 This is something that we'd have to get setup and working. |
FWIW, you can generate this data as follows:
|
@maohong You can see results from my up-to-date fork in the description here: #14333 A couple of notes:
|
Got it! Thanks @mattlord |
Just an update that we finally got things setup and working as we'd like (e.g. enabling cross package coverage) and the number is now at 71% as you can see in the badge and its link: https://github.com/vitessio/vitess/blob/main/README.md That's still without including the endtoend tests, which we still want to do (will be more involved, however). |
Question
Hi,
We are investigating Vitess and considering using Vitess in live, just wondering what is the current test coverage of the code base? I tried to find this data but could't find it.
Thanks
The text was updated successfully, but these errors were encountered: