-
-
Notifications
You must be signed in to change notification settings - Fork 150
Add CI workflow to run integration tests and to test Go code #659
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
Conversation
On every push and pull request that affects relevant files, run the project's Go code tests.
On every push and pull request that affects relevant files, run the integration tests.
… when checking out on a Windows runner.
…`test-go-task` and `test-go-integration-task` workflows
Codecov Report
@@ Coverage Diff @@
## main #659 +/- ##
======================================
Coverage ? 8.46%
======================================
Files ? 65
Lines ? 5046
Branches ? 0
======================================
Hits ? 427
Misses ? 4565
Partials ? 54
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work Umberto!
… Go code (#659) * Add CI workflow to test Go code On every push and pull request that affects relevant files, run the project's Go code tests. * rename test dir to tests (for uniformity with other tooling team repos) * Add CI workflow to run integration tests On every push and pull request that affects relevant files, run the integration tests. * add again step to install dependencies (used by systray) * disable actions/checkout action conversion of LF line endings to CRLF when checking out on a Windows runner. * remove testing from the release workflow, since it's already done in `test-go-task` and `test-go-integration-task` workflows * update release CI to use the new `task go:build`
Please check if the PR fulfills these requirements
before creating one)
CI change
The CI workflow that runs the test is old, outdated, and it's difficult to maintain
On every push and pull request that affects relevant files, run the project's Go code tests andintegration tests.
no