-
Notifications
You must be signed in to change notification settings - Fork 3
SEAB-5247: Add MuteForSuccessfulTests extension to CLI #224
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
SEAB-5247: Add MuteForSuccessfulTests extension to CLI #224
Conversation
Codecov ReportBase: 69.73% // Head: 69.37% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #224 +/- ##
=============================================
- Coverage 69.73% 69.37% -0.37%
+ Complexity 1076 1046 -30
=============================================
Files 47 47
Lines 6050 6050
Branches 796 796
=============================================
- Hits 4219 4197 -22
- Misses 1510 1515 +5
- Partials 321 338 +17
Flags with carried forward coverage won't be shown. Click here to find out more.
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. |
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.
which there are not, thanks!
@ExtendWith(SystemStubsExtension.class) | ||
@ExtendWith(MuteForSuccessfulTests.class) | ||
@ExtendWith(BaseIT.TestStatus.class) |
There was a problem hiding this comment.
Choose a reason f B7A2 or hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BaseIT
redundant here, but probably not worth fixing unless there are other issues
Description
This PR adds our new
MuteForSuccessfulTests
Junit 5 extension to the CLI tests.Important changes include:
dockstore-core.version
to1.14.0-alpha.7
(to reference the new extension).confidential4
paths to.gitignore
, even though they're not included in the bundle, because I'd added them for another change that got reverted, but there's no harm in leaving them.Review Instructions
Find a failed CircleCI run that incorporates these changes and confirm that the stdout/stderr output is included with, and only with, the failures.
Issue
https://ucsc-cgl.atlassian.net/browse/SEAB-5247
Security
If there are any concerns that require extra attention from the security team, highlight them here.
Please make sure that you've checked the following before submitting your pull request. Thanks!
./mvnw clean install