[dashboard] replace panel_context_menu functional tests with unit tests#226876
[dashboard] replace panel_context_menu functional tests with unit tests#226876nreese merged 4 commits intoelastic:mainfrom
Conversation
|
/ci |
1 similar comment
|
/ci |
|
/ci |
|
/ci |
|
Pinging @elastic/kibana-presentation (Team:Presentation) |
|
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
History
|
ThomThomson
left a comment
There was a problem hiding this comment.
Great work to remove these tests. Spent a few minutes ensuring that we had unit test coverage already for cloning and editing panels + looked through the code. LGTM!
| await browser.get(currentUrl.toString(), false); | ||
| }); | ||
|
|
||
| describe('visualization object edit menu', () => { |
There was a problem hiding this comment.
Great to see removal of this legacy vis code leaking into Dashboard.
| it('are hidden in view mode', async function () { | ||
| await dashboard.saveDashboard(dashboardName); | ||
|
|
||
| await dashboardPanelActions.expectMissingEditPanelAction(); |
There was a problem hiding this comment.
Looks like we had redundant coverage for this in src/platform/plugins/private/presentation_panel/public/panel_actions/edit_panel_action/edit_panel_action.test.tsx. Nice to see the FTR coverage removed.
|
Starting backport for target branches: 8.19, 9.1 |
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
…ts (elastic#226876) Test cases in panel_context_menu are better suited for unit tests instead of functional tests. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Test cases in panel_context_menu are better suited for unit tests instead of functional tests.