-
Notifications
You must be signed in to change notification settings - Fork 125
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
test: Code coverage for e2e tests #1475
Conversation
What are those numbers on the right? Is it really counting all packages? |
I'm using gocov for coverage analysis.
Packages coverage after running all E2E tests
I've removed all
Or coverage of registry package from internal of kvscheduler plugin
|
484f335
to
18e08e9
Compare
Codecov Report
@@ Coverage Diff @@
## dev #1475 +/- ##
======================================
Coverage ? 52.12%
======================================
Files ? 544
Lines ? 65827
Branches ? 0
======================================
Hits ? 34314
Misses ? 29274
Partials ? 2239
Continue to review full report at Codecov.
|
test-e2e
64e36f9
to
29c7ddb
Compare
upload unittests coverage to coveralls was intentionally left there. I think that it would be better to remove it after some time with codecov |
test-e2e
* Initial collecting coverage for e2e tests * Allow to run e2e tests with and without coverage * Add build tag to dummy test, so it is skipped in general case * Upload coverage to codecov test-e2e
Created a dummy test that executes
main()
ofvpp-agent
. Each e2e test starts that executable with enabled coverage analysis. All coverage data will be stored in/tmp/e2e-coverage
directory and after merged with gocovmerge to one/tmp/e2e-all.out
file.The idea of how coverage could be collected was borrowed from "Go coverage with external tests".