-
Notifications
You must be signed in to change notification settings - Fork 319
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
chore: use gotestsum for test execution #2586
Conversation
Codecov ReportBase: 43.99% // Head: 43.94% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #2586 +/- ##
==========================================
- Coverage 43.99% 43.94% -0.05%
==========================================
Files 187 187
Lines 39086 39086
==========================================
- Hits 17197 17178 -19
- Misses 20808 20827 +19
Partials 1081 1081
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
23a3b44
to
c01cf11
Compare
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.
I especially like disabling logs by default, it has become to hard to investigate an issue.
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.
Nice change! tried to see if other tools like GoConvey have similar functionality but they cause more confusion than gain.
Description
Running tests with
gotestsum
simplifies the console's output and makes it easier to identify test failures, since only logs from the failed tests are included.✓ . (1m43.657s) (coverage: 78.7% of statements) ∅ admin ∅ admin/profiler ∅ app ∅ app/apphandlers ✓ app/cluster (3.591s) (coverage: 71.6% of statements) ✓ app/cluster/state (1.677s) (coverage: 74.3% of statements) ∅ build/wait-for-go ∅ cmd/devtool ∅ cmd/devtool/commands ✓ config (7ms) (coverage: 69.5% of statements) ✓ config/backend-config (16.917s) (coverage: 59.8% of statements) ...
If still, for any reason, the full logs from all tests are required, you may enable debug logging
Security