chore(ci): add workflow to generate test coverage and report to DeepSource#177
chore(ci): add workflow to generate test coverage and report to DeepSource#177MashyBasker wants to merge 8 commits intoDeepSourceCorp:masterfrom
Conversation
…urce Signed-off-by: Maharshi Basu <basumaharshi10@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
Signed-off-by: Maharshi Basu <basumaharshi10@gmail.com>
Signed-off-by: Maharshi Basu <basumaharshi10@gmail.com>
Signed-off-by: Maharshi Basu <basumaharshi10@gmail.com>
Signed-off-by: Maharshi Basu <basumaharshi10@gmail.com>
Signed-off-by: Maharshi Basu <basumaharshi10@gmail.com>
Signed-off-by: Maharshi Basu <basumaharshi10@gmail.com>
| @@ -1,3 +1,5 @@ | |||
| //go:build exclude | |||
There was a problem hiding this comment.
Is there a better way to do these exclusions instead of having to add them in every checker?
There was a problem hiding this comment.
We can place test files inside a folder prefixed with an underscore (e.g., _testdata). However, the YAML test runner currently only looks for tests in the current directory. Once we add support for test folders in YAML-based checkers, we can remove the exclusion directives.
.github/workflows/main.yml
Outdated
| @@ -0,0 +1,35 @@ | |||
| name: automatic-test-coverage-report | |||
There was a problem hiding this comment.
This workflow should simply be named "run unit tests" or something. Reporting coverage is a part of running the test suite.
There was a problem hiding this comment.
Addressed in latest commit.
Signed-off-by: Maharshi Basu <basumaharshi10@gmail.com>
|
@unnxt30 is working on test coverage reporting in a separate PR. |
Purpose
Adds a workflow to generate test reports for Go code and sends the coverage to DeepSource.