[
https://issues.apache.org/jira/browse/YUNIKORN-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18043893#comment-18043893
]
Peter Bacsko edited comment on YUNIKORN-2135 at 12/9/25 3:58 PM:
-----------------------------------------------------------------
This ticket seems to be abandoned and the PRs are stale. Unless there is a
compelling reason, I suggest closing. Coverage data from integration tests is
not meaningless, but those tests should focus on API endpoints and higher level
use-cases anyway, not on coverage.
was (Author: pbacsko):
This ticket seems to be abandoned and the PRs are stale. Unless there is a
compelling reason, I suggest closing. Coverage data from integration tests is
not meaningless, but those tests should focus on API endpoint and higher level
use-cases anyway, not on coverage.
> Add integration test code coverage
> ----------------------------------
>
> Key: YUNIKORN-2135
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2135
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: test - e2e
> Reporter: PoAn Yang
> Assignee: PoAn Yang
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2023-11-16-18-56-07-624.png
>
>
> From [https://go.dev/testing/coverage/]:
> > Beginning in Go 1.20, Go supports collection of coverage profiles from
> > applications and from integration tests, larger and more complex tests for
> > Go programs.
> We have many integration test cases with ginkgo. It's good to have a new code
> coverage with golang new feature. We can use different
> [flags|https://github.com/codecov/codecov-action#usage] to submit
> unit/integration test code coverage to codecov.
>
> Ref: [https://go.dev/blog/integration-test-coverage]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
