OCPBUGS-63471: Update e2e to reflect new UI

Author: logonoff

frontend/packages/dev-console/integration-tests/features/customization/customization-of-pinned-resource.feature

@@ -13,26 +13,26 @@ Feature: Customization of pre-pinned resources
              When user navigates to Cluster configuration page
               And user clicks on Developer tab
              Then user should see Pre-pinned navigation items section
- 
+
         @regression @manual
         Scenario: When pre-pinned resources customization is not added: DC-02-TC02
             Given user is at "operator.openshift.io/v1" console details page
-              And user selects "Customize" in the Actions menu
+              And user clicks the "Customize" button in the page heading
               And user selects "Developer" tab in "Cluster configuration" page
              Then user should see default pins from extension under "Pinned Resources" in "Pre-pinned navigation items"
 
         @regression @manual
         Scenario: When resource is selected for pre-pinned navigation: DC-02-TC03
             Given user is at "operator.openshift.io/v1" console details page
-              And user selects "Customize" in the Actions menu
+              And user clicks the "Customize" button in the page heading
               And user selects "Developer" tab in "Cluster configuration" page
              When user selects "Deployment" under "Resources" and added to "Pinned Resources"
              Then user should see "Deployment" resource details in "operator.openshift.io/v1" console YAML under spec.customization.perspectives.id.pinnedResources for id 'dev'
- 
+
         @regression @manual
         Scenario: When resource is removed from pre-pinned navigation: DC-02-TC04
             Given user is at "operator.openshift.io/v1" console details page
-              And user selects "Customize" in the Actions menu
+              And user clicks the "Customize" button in the page heading
               And user selects "Developer" tab in "Cluster configuration" page
              When user selects "Deployment" under "Pinned Resources" and moved back "Resources"
              Then user should not see "Deployment" resource details in "operator.openshift.io/v1" console YAML under spec.customization.perspectives.id.pinnedResources for id 'dev'

frontend/packages/dev-console/integration-tests/features/e2e/enable-dev-perspective-ci.feature

@@ -6,15 +6,14 @@ Feature: Enable dev perspective
             Given user has only admin perspective enabled
               And user has logged in as admin user
 
- 
+
         Scenario: Enable dev perspective: P-01-TC04
             Given user is at admin perspective
               And user is at Search page in Home section
               And user searches "console"
               And user clicks on cluster
-              And user selects "Customize" from actions menu
+              And user clicks the "Customize" button in the page heading
               And user selects "Enabled" in the Developer under perspective section of general customisation
              Then user will see Saved alert
               And user refreshes the page to see developer option
               And user will see developer perspective in the perspective switcher
-

frontend/packages/dev-console/integration-tests/features/perspectives/configure-perspectives.feature

@@ -5,7 +5,7 @@ Feature: Configure perspectives
 
         Background:
             Given user has logged in as admin user
- 
+
         @regression @manual
         Scenario: Configuring available perspectives: P-01-TC01
             Given user is at cluster YAML of "operator.openshift.io/v1" console
@@ -45,9 +45,8 @@ Feature: Configure perspectives
               And user searches "console"
               And user clicks on cluster
             #   And user selects "operator.openshift.io" console
-              And user selects "Customize" from actions menu
+              And user clicks the "Customize" button in the page heading
               And user selects "Enabled" in the Developer under perspective section of general customisation
              Then user will see Saved alert
               And user refreshes the page to see developer option
               And user will see developer perspective in the perspective switcher
-

frontend/packages/dev-console/integration-tests/support/step-definitions/customization/configure-perspectives.ts

@@ -70,9 +70,8 @@ When('user clicks on cluster', () => {
   cy.byTestID('cluster').should('be.visible').click({ force: true });
 });
 
-When('user selects {string} from actions menu', (item: string) => {
-  cy.byLegacyTestID('actions-menu-button').should('be.visible').click();
-  cy.get(`[data-test-action="${item}"] button`).should('be.visible').click();
+When('user clicks the {string} button in the page heading', (item: string) => {
+  cy.get(`button[data-test-action="${item}"]`).should('be.visible').click();
   cy.get('[data-test="page-heading"] h1').should('have.text', 'Cluster configuration');
 });