-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[ResponseOps][Cases] clear query cache for cases flaky tests #191212
[ResponseOps][Cases] clear query cache for cases flaky tests #191212
Conversation
/ci |
/ci |
/ci |
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/response-ops-cases (Feature:Cases) |
let appMockRenderer: AppMockRenderer; | ||
|
||
beforeEach(() => { | ||
appMockRenderer = createAppMockRenderer(); | ||
jest.clearAllMocks(); | ||
}); | ||
|
||
afterEach(() => { | ||
appMockRenderer.queryClient.getQueryCache().clear(); |
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.
Would be nice to have just one appMockRenderer.cleanup function that does everything. If there is something to change there would be just one place to update, wdyt?
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.
Updated in 904fb11
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
To update your PR or re-run it, just comment with: |
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.
🤞
Summary
Clear query cache to fix flakiness of jest unit tests in cases plugin.
Checklist