Skip to content
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

[Cases] Unskip filter popover, property actions flaky tests #177611

Merged

Conversation

js-jankisalvi
Copy link
Contributor

Summary

As a follow-up to #176863 unskipping filterPopOver and propertyActions tests

Fixes #176679
Fixes #176680
Fixes #176681
Fixes #176682
Fixes #176683
Fixes #176684
Fixes #176685
Fixes #176686
Fixes #174384
Fixes #174667
Fixes #175310

@js-jankisalvi js-jankisalvi added release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Cases Cases feature v8.14.0 labels Feb 22, 2024
@js-jankisalvi js-jankisalvi self-assigned this Feb 22, 2024
@js-jankisalvi js-jankisalvi requested a review from a team as a code owner February 22, 2024 15:37
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops-cases (Feature:Cases)

Copy link
Contributor

@adcoelho adcoelho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved, no need to do this but I was thinking about the following:

Tiago mentioned in our call Tuesday that some tests are async when they shouldn't be.

I found a few in the files in this PR:

  • alert_property_actions.test.tsx
    • line 86
  • registered_attachments_property_actions.test.tsx
    • line 88
    • line 95
  • user_comment_property_actions.test.tsx
    • line 101

@js-jankisalvi
Copy link
Contributor Author

Tiago mentioned in our call Tuesday that some tests are async when they shouldn't be.

Yeah I was thinking this and then thought let's first see if current changes are working or not. 😄
And then maybe we can refactor with async in all files in one PR!!

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

✅ unchanged

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @js-jankisalvi

@js-jankisalvi js-jankisalvi merged commit 9bdea88 into elastic:main Feb 22, 2024
27 checks passed
@kibanamachine kibanamachine added the backport:skip This commit does not require backporting label Feb 22, 2024
fkanout pushed a commit to fkanout/kibana that referenced this pull request Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting Feature:Cases Cases feature release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v8.14.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Failing test: Jest Tests.x-pack/plugins/cases/public/components/filter_popover - FilterPopover renders empty label correctly Failing test: Jest Tests.x-pack/plugins/cases/public/components/user_actions/property_actions - UserCommentPropertyActions renders the correct number of actions Failing test: Jest Tests.x-pack/plugins/cases/public/components/filter_popover - FilterPopover renders string type options correctly Failing test: Jest Tests.x-pack/plugins/cases/public/components/user_actions/property_actions - AlertPropertyActions renders the correct number of actions Failing test: Jest Tests.x-pack/plugins/cases/public/components/user_actions/property_actions - RegisteredAttachmentsPropertyActions renders the correct number of actions
5 participants