Investigating Functional Test Failures in Upgrade Assistant#95440
Investigating Functional Test Failures in Upgrade Assistant#95440cuff-links wants to merge 3 commits intoelastic:masterfrom
Conversation
|
Going to re-enable these tests. Ran 100 times in flaky test runner without any failures. https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/1403/ |
…rade_Assistant_UI_Test_Failures
|
Just happened to notice this draft PR. I wanted to point out that the tests themselves will likely need to be refactored now that we hide most of the UA UI (related work: #92834). You can take a look at the UA a11y tests as an example on how to handle this. |
|
Closed in favor of #96714 |
💔 Build Failed
Failed CI Steps
Test FailuresKibana Pipeline / general / Chrome UI Functional Tests.test/functional/apps/saved_objects_management/show_relationships·ts.saved objects management saved objects relationships flyout "before each" hook for "displays the invalid references"Standard OutStack TraceKibana Pipeline / general / Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/canvas.Canvas app "after all" hook in "Canvas app"Standard OutStack TraceKibana Pipeline / general / Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/canvas/feature_controls/canvas_spaces·ts.Canvas app spaces feature controls space with Canvas disabled "before all" hook for "doesn't show canvas navlink"Standard OutStack Traceand 16 more failures, only showing the first 3. Metrics [docs]Saved Objects .kibana field count
History
To update your PR or re-run it, just comment with: |
Summary
Closes #86546
This PR was created to run the Upgrade Assistant tests in isolation through the flaky test runner to investigate the cause of test failures.