Skip to content
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

ci: Run go test, upload results to CodeClimate #295

Merged
merged 1 commit into from
Apr 8, 2020

Conversation

jwflory
Copy link
Member

@jwflory jwflory commented Apr 4, 2020

I also changed our test suite to test on Go 1.14.x instead of latest Go
master, since I think it makes more sense to test on stable Go code than
the latest changes. Even if Go master tests failed, to me, it wouldn't
necessarily block a PR. Just tell us that something might be changing
soon, eventually, someday™.

Shout-out to @Zedjones for helping us figure this out in the developer
meeting today.

@jwflory jwflory added improvement Improves on something that already exists quality assurance CI tests, unit tests, integration tests, any kind of testing labels Apr 4, 2020
@jwflory jwflory requested a review from a team April 4, 2020 19:26
@jwflory jwflory self-assigned this Apr 4, 2020
@jwflory jwflory added the blocked Progress blocked by another task or issue label Apr 4, 2020
@jwflory
Copy link
Member Author

jwflory commented Apr 4, 2020

Hmm, running into issues with CodeClimate. It's not uploading the test output. Give me some time next week to debug this. For now, this PR is not ready to merge yet.

@jwflory jwflory added needs changes Needs changes or fixes before closing and removed blocked Progress blocked by another task or issue labels Apr 4, 2020
I also changed our test suite to test on Go 1.14.x instead of latest Go
master, since I think it makes more sense to test on stable Go code than
the latest changes. Even if Go `master` tests failed, to me, it wouldn't
necessarily block a PR. Just tell us that something might be changing
soon, eventually, someday™.

Shout-out to @Zedjones for helping us figure this out in the developer
meeting today.

This also adds a snazzy test coverage badge to our README. This will
render correctly once this PR builds on `master`.

Signed-off-by: Justin W. Flory <git@jwf.io>
@jwflory jwflory removed the needs changes Needs changes or fixes before closing label Apr 7, 2020
@jwflory
Copy link
Member Author

jwflory commented Apr 7, 2020

This is now working. It took a little bit of figuring out since the docs weren't fantastic. But I verified this did upload a test coverage report up to CodeClimate. Not sure if this is a public URL or not:

https://codeclimate.com/repos/580966949256861b2f0074ee/settings/test_reports/5e8ceae27e91f03b79009cc1

This should start working and showing our total project test coverage once this builds and runs on master.

Copy link
Member

@Tjzabel Tjzabel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💯

@jwflory
Copy link
Member Author

jwflory commented Apr 8, 2020

Super! Let's see how this goes. Merging! 🎬

@jwflory jwflory merged commit 5edf1fc into RITlug:master Apr 8, 2020
@jwflory jwflory deleted the change/run-tests branch April 8, 2020 01:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improves on something that already exists quality assurance CI tests, unit tests, integration tests, any kind of testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants