-
Notifications
You must be signed in to change notification settings - Fork 2.3k
[Feature/extensions] Restructured testExtensionsInitialize #4029
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
[Feature/extensions] Restructured testExtensionsInitialize #4029
Conversation
Signed-off-by: Ryan Bogan <rbogan@amazon.com>
Gradle Check (Jenkins) Run Completed with:
|
Codecov Report
@@ Coverage Diff @@
## feature/extensions #4029 +/- ##
========================================================
- Coverage 70.64% 70.61% -0.03%
- Complexity 56884 57000 +116
========================================================
Files 4584 4597 +13
Lines 273654 274339 +685
Branches 40105 40187 +82
========================================================
+ Hits 193318 193729 +411
- Misses 64085 64339 +254
- Partials 16251 16271 +20
Help us with your feedback. Take ten seconds to tell us how you rate us. |
extensionsOrchestrator.extensionsInitialize(); | ||
mockLogAppender.assertAllExpectationsMatched(); | ||
} | ||
extensionsOrchestrator.extensionsInitialize(); |
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.
What exactly are we testing here?
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 see what you're saying, will approach a different way
Gradle Check (Jenkins) Run Completed with:
|
Signed-off-by: Ryan Bogan <rbogan@amazon.com>
…ch into fix_orchestrator_test
Signed-off-by: Ryan Bogan <rbogan@amazon.com>
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Signed-off-by: Ryan Bogan <rbogan@amazon.com>
Gradle Check (Jenkins) Run Completed with:
|
@@ -245,68 +245,7 @@ public void testEmptyExtensionsFile() throws Exception { | |||
expectThrows(IOException.class, () -> new ExtensionsOrchestrator(settings, extensionDir)); | |||
} | |||
|
|||
public void testExtensionsInitialize() throws Exception { |
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.
Do you just want to do @Ignore
for now? [1]
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.
This is better than removing the test.
You can ignore it like mentioned below and add the issue to it.
@Ignore("<Issue Link>")
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.
Ignore is on the forbiddenApisList
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.
Ran into this issue when I was removing User
. I ended up keeping the whole test, but commenting-out the final assertion and adding an assertion that was logically opposite. See here for example.
In this case, change the two SeenEventExpectation
constructors to UnseenEventExpectation
with a comment pointing to the issue so when your inverted test eventually fails, whoever is debugging it (possibly you) instantly knows how to toggle it back.
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.
The only problem with this solution is that the tests as is passes on local machines, but not in Jenkins. So by changing the expectations to "Unseen", the PR gradle check would pass but after that the local gradle checks would fail for everyone.
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 think if I just comment out the assert statements and add a similar message to yours, then the same functionality that you are suggesting could be implemented.
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.
its nice to see we have checks every where :)
@@ -245,68 +245,7 @@ public void testEmptyExtensionsFile() throws Exception { | |||
expectThrows(IOException.class, () -> new ExtensionsOrchestrator(settings, extensionDir)); | |||
} | |||
|
|||
public void testExtensionsInitialize() throws Exception { |
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.
Ran into this issue when I was removing User
. I ended up keeping the whole test, but commenting-out the final assertion and adding an assertion that was logically opposite. See here for example.
In this case, change the two SeenEventExpectation
constructors to UnseenEventExpectation
with a comment pointing to the issue so when your inverted test eventually fails, whoever is debugging it (possibly you) instantly knows how to toggle it back.
Signed-off-by: Ryan Bogan <rbogan@amazon.com>
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Signed-off-by: Ryan Bogan rbogan@amazon.com
Description
Fixes the gradle check failure for testExtensionsInitialize
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.