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

OCPBUGS-24592: Fix CI tests in helm and devconsole packages #13464

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Expand Up @@ -9,7 +9,7 @@ Feature: Create Application from Devfile
And user is at Add page


@regression @broken-test
@regression
Scenario: Deploy git workload with devfile from topology page: A-04-TC01
Given user is at the Topology page
When user right clicks on topology empty graph
Expand All @@ -31,7 +31,7 @@ Feature: Create Application from Devfile
And user is able to see workload "node-example" in topology page


@regression
@regression @broken-test
Scenario: No service is shown in the node sidebar if it is not defined in the devfile : A-04-TC03
Given user has created workload "node-example" with resource type "Deployment"
And user is at Topology page
Expand All @@ -40,7 +40,7 @@ Feature: Create Application from Devfile
And user can see under Services section "No Services found for this resource."


@regression
@regression @broken-test
Scenario: No route is shown in the node sidebar if it is not defined in the devfile : A-04-TC04
Given user has created workload "node-example" with resource type "Deployment"
And user is at Topology page
Expand Down
Expand Up @@ -86,7 +86,6 @@ Feature: Create the different workloads from Add page
Then user will be redirected to Topology page
And user is able to see workload "mariadb" in topology page

@regression @broken-test
Scenario: Deploy git workload with devfile from topology page: A-04-TC01
Given user is at the Topology page
When user right clicks on topology empty graph
Expand Down
Expand Up @@ -8,7 +8,9 @@ When('user right clicks on topology empty graph', () => {

When('user selects {string} option from Add to Project context menu', (option: string) => {
cy.get(topologyPO.graph.contextMenuOptions.addToProject).focus().trigger('mouseover');
cy.byTestActionID(option).click({ force: true });
cy.get(`[data-test-action="${option}"] button[role="menuitem"]`)
.should('be.visible')
.click({ force: true });
});

When('user enters Git Repo url {string} in Devfile page', (gitUrl: string) => {
Expand Down
Expand Up @@ -38,7 +38,7 @@ Feature: Helm Release
Then user will be redirected to Topology page
And Topology page have the helm chart workload "nodejs-release"

@regression @broken-test

Scenario: Context menu options of helm release: HR-01-TC01
Given user is at the Topology page
When user right clicks on the helm release "nodejs-release" to open the context menu
Expand Down
Expand Up @@ -42,7 +42,7 @@ Then(
);

Then('user is able to see the context menu with actions Upgrade and Delete Helm Release', () => {
cy.get('ul[role="menu"]').should('be.visible');
cy.get('div.odc-topology-context-menu').should('be.visible');
cy.byTestActionID('Upgrade').should('be.visible');
cy.byTestActionID('Delete Helm Release').should('be.visible');
});
Expand Down
Expand Up @@ -63,7 +63,7 @@ export const topologyPO = {
showPodCount: '[id$=show-pod-count]',
},
contextMenuOptions: {
addToProject: '.pf-topology-context-sub-menu',
addToProject: 'button.pf-topology-context-sub-menu',
},
addLink: '[data-test="add-page"]',
quickSearch: '[data-test="quick-search-bar"]',
Expand Down