-
Notifications
You must be signed in to change notification settings - Fork 159
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
Refactor running unit tests #121
Comments
It looks like this is already a seperate check. |
I've also verified that the exit code does indeed propagate correctly, although there is no feedback as to which test failed without reading the Junit report. I'll open an (optional) PR to address that but based on the description of the issue I think this can be closed. |
dave-tucker
added a commit
to dave-tucker/eve
that referenced
this issue
Nov 16, 2019
This commit uses the gotestsum tool to run unit tests. gotestsum provides human-readable output from go test while also outputting a Junit XML file. Relates-To: lf-edge#121 Signed-off-by: Dave Tucker <dave@dtucker.co.uk>
rvs
pushed a commit
that referenced
this issue
Nov 16, 2019
This commit uses the gotestsum tool to run unit tests. gotestsum provides human-readable output from go test while also outputting a Junit XML file. Relates-To: #121 Signed-off-by: Dave Tucker <dave@dtucker.co.uk>
Done by @dave-tucker |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unit tests need to be put into a separate check in the circle pipeline and we also need to make sure make test target returns non-0 exit code if tests fail
The text was updated successfully, but these errors were encountered: