ODC-7492: automation for sample-card-add-page feature file

[The-Anton]

Description:

• Automation of sample-card-add-page gherkin file in getting-started package

Jira Id:

• Story:
  - ODC-7492

Checks for approving Epic scenarios Automation PR:

• Execute the @to-do tagged gherkin scripts manually
• Convert the @to-do gherkin scripts to cypress automation scripts
• Once scripts are automated, replace tag @to-do with @epic-number
• Execute the scripts in Remote cluster

Refactoring criteria for approving Automation PR:

• update the test cases count in Automation status confluence Report

Execution Commands:
Example:

    export NO_HEADLESS=true && export CHROME_VERSION=$(/usr/bin/google-chrome-stable --version)
    BRIDGE_KUBEADMIN_PASSWORD=YH3jN-PRFT2-Q429c-5KQDr
    BRIDGE_BASE_ADDRESS=https://console-openshift-console.apps.dev-svc-4.13-042801.devcluster.openshift.com/
    export BRIDGE_KUBEADMIN_PASSWORD
    export BRIDGE_BASE_ADDRESS
    oc login -u kubeadmin -p $BRIDGE_KUBEADMIN_PASSWORD
    oc apply -f ./frontend/integration-tests/data/htpasswd-secret.yaml
    oc patch oauths cluster --patch "$(cat ./frontend/integration-tests/data/patch-htpasswd.yaml)" --type=merge
    ./test-cypress.sh -p dev-console

Screen shots:

Browser conformance:

• Chrome
• Firefox
• Safari
• Edge

[openshift-ci-robot]

@The-Anton: This pull request references ODC-7492 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

In response to this:

Description:

• Automation of sample-card-add-page gherkin file in getting-started package

Jira Id:

• Story:
  • ODC-7492

Checks for approving Epic scenarios Automation PR:

• Execute the @to-do tagged gherkin scripts manually
• Convert the @to-do gherkin scripts to cypress automation scripts
• Once scripts are automated, replace tag @to-do with @epic-number
• Execute the scripts in Remote cluster

Refactoring criteria for approving Automation PR:

• update the test cases count in Automation status confluence Report

Execution Commands:
Example:

   export NO_HEADLESS=true && export CHROME_VERSION=$(/usr/bin/google-chrome-stable --version)
   BRIDGE_KUBEADMIN_PASSWORD=YH3jN-PRFT2-Q429c-5KQDr
   BRIDGE_BASE_ADDRESS=https://console-openshift-console.apps.dev-svc-4.13-042801.devcluster.openshift.com/
   export BRIDGE_KUBEADMIN_PASSWORD
   export BRIDGE_BASE_ADDRESS
   oc login -u kubeadmin -p $BRIDGE_KUBEADMIN_PASSWORD
   oc apply -f ./frontend/integration-tests/data/htpasswd-secret.yaml
   oc patch oauths cluster --patch "$(cat ./frontend/integration-tests/data/patch-htpasswd.yaml)" --type=merge
   ./test-cypress.sh -p dev-console

Screen shots:

Browser conformance:

• Chrome
• Firefox
• Safari
• Edge

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[sanketpathak]

Tests run green

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sanketpathak, The-Anton

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• frontend/packages/dev-console/integration-tests/OWNERS [sanketpathak]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sanketpathak]

PR only updates e2e tests
/label docs-approved
/label px-approved
/label qe-approved

[openshift-ci-robot]

@The-Anton: This pull request references ODC-7492 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

In response to this:

Description:

• Automation of sample-card-add-page gherkin file in getting-started package

Jira Id:

• Story:
  • ODC-7492

Checks for approving Epic scenarios Automation PR:

• Execute the @to-do tagged gherkin scripts manually
• Convert the @to-do gherkin scripts to cypress automation scripts
• Once scripts are automated, replace tag @to-do with @epic-number
• Execute the scripts in Remote cluster

Refactoring criteria for approving Automation PR:

• update the test cases count in Automation status confluence Report

Execution Commands:
Example:

   export NO_HEADLESS=true && export CHROME_VERSION=$(/usr/bin/google-chrome-stable --version)
   BRIDGE_KUBEADMIN_PASSWORD=YH3jN-PRFT2-Q429c-5KQDr
   BRIDGE_BASE_ADDRESS=https://console-openshift-console.apps.dev-svc-4.13-042801.devcluster.openshift.com/
   export BRIDGE_KUBEADMIN_PASSWORD
   export BRIDGE_BASE_ADDRESS
   oc login -u kubeadmin -p $BRIDGE_KUBEADMIN_PASSWORD
   oc apply -f ./frontend/integration-tests/data/htpasswd-secret.yaml
   oc patch oauths cluster --patch "$(cat ./frontend/integration-tests/data/patch-htpasswd.yaml)" --type=merge
   ./test-cypress.sh -p dev-console

Screen shots:

Browser conformance:

• Chrome
• Firefox
• Safari
• Edge

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@The-Anton: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.