mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
# Backport This will backport the following commits from `main` to `8.18`: - [[Response Ops][Flaky Tests] Remove duplicated click creating connector (#216145)](https://github.com/elastic/kibana/pull/216145) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julian Gernun","email":"17549662+jcger@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-28T11:43:25Z","message":"[Response Ops][Flaky Tests] Remove duplicated click creating connector (#216145)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202328\n\nThe test itself wasn't failing but the setup was. The test failing does\nso because it's the first one in the test suite. We are trying to click\non the flyout save button twice one right after the other. What I think\nis happening is that the first one manages to close the flyout before\nthe second click gets the chance to trigger.\n\nAlso the image in CI is this where we can see the flyout is closed\nalready but it's still trying to close it\n\n","sha":"e16ba346e39df1843b45017137d4c894c357bb13","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","backport:version","v8.18.0","v9.1.0"],"title":"[Response Ops][Flaky Tests] Remove duplicated click creating connector","number":216145,"url":"https://github.com/elastic/kibana/pull/216145","mergeCommit":{"message":"[Response Ops][Flaky Tests] Remove duplicated click creating connector (#216145)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202328\n\nThe test itself wasn't failing but the setup was. The test failing does\nso because it's the first one in the test suite. We are trying to click\non the flyout save button twice one right after the other. What I think\nis happening is that the first one manages to close the flyout before\nthe second click gets the chance to trigger.\n\nAlso the image in CI is this where we can see the flyout is closed\nalready but it's still trying to close it\n\n","sha":"e16ba346e39df1843b45017137d4c894c357bb13"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216145","number":216145,"mergeCommit":{"message":"[Response Ops][Flaky Tests] Remove duplicated click creating connector (#216145)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202328\n\nThe test itself wasn't failing but the setup was. The test failing does\nso because it's the first one in the test suite. We are trying to click\non the flyout save button twice one right after the other. What I think\nis happening is that the first one manages to close the flyout before\nthe second click gets the chance to trigger.\n\nAlso the image in CI is this where we can see the flyout is closed\nalready but it's still trying to close it\n\n","sha":"e16ba346e39df1843b45017137d4c894c357bb13"}}]}] BACKPORT--> Co-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>
This commit is contained in:
parent
0bc14342fb
commit
24c65a5dcc
1 changed files with 0 additions and 1 deletions
|
@ -64,7 +64,6 @@ export default ({ getPageObjects, getService }: FtrProviderContext) => {
|
|||
await find.clickByCssSelector(
|
||||
'[data-test-subj="create-connector-flyout-save-btn"]:not(disabled)'
|
||||
);
|
||||
await testSubjects.click('create-connector-flyout-save-btn');
|
||||
});
|
||||
|
||||
const toastTitle = await toasts.getTitleAndDismiss();
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue