Cypress e2e Project Creation/Deletion

[antowaddle]

https://issues.redhat.com/browse/RHOAIENG-14367

Description

Migration of the below Robot test to Cypress

ODS-1775

https://opendatascience-jenkins-csb-rhods.apps.ocp-c1.prod.psi.redhat.com/job/rhoai/job/2.13/job/selfmanaged/job/cli/job/aws/job/rhoai-smoke/1/robot/report/log.html#s1-s4-s2-s4-s1-t3 

How Has This Been Tested?

• An oc login should be performed in the cluster before running the test
• test-variables.yml should be configured properly
• Export the path to the test-variables.yml: $ export CY_TEST_CONFIG=<path_to>/test-variables.yml

How to run

After exporting the test-variables.yml we have 2 different ways:

Using the UI
Go to odh-dashboard/frontend/src/tests/cypress and run the command npx cypress open . This will open the Cypress UI where verifyDSPCreation.cy.ts can be run.

Headless
Go to odh-dashboard/frontend/src/tests/cypress and run the command npx cypress run --spec "cypress/tests/e2e/dataScienceProjects/testProjectCreation.cy.ts" --browser chrome

How Has This Been Tested?

Locally, against a live cluster.

Test Impact

This is already a test

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

After the PR is posted & before it merges:

• The developer has tested their solution on a cluster by using the image produced by the PR to main

This PR also introduces a plugin - https://github.com/filiphric/cypress-plugin-steps This plugin will display text contained within cy.step('...') numbered and highlighted on the Cypress Console to allow for improved test bugging, maintainability and readability.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.87%. Comparing base (538a8ff) to head (5c2f26e).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3388      +/-   ##
==========================================
- Coverage   85.89%   85.87%   -0.02%     
==========================================
  Files        1338     1338              
  Lines       30127    30127              
  Branches     8274     8274              
==========================================
- Hits        25877    25872       -5     
- Misses       4250     4255       +5     

see 5 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 538a8ff...5c2f26e. Read the comment docs.

[manosnoam]

Thanks @antowaddle for your first PR!
See some suggestions I have.

[FedeAlonso]

/lgtm

[manosnoam]

Looks good, thanks!

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: FedeAlonso, manosnoam

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/OWNERS [manosnoam]

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

[jiridanek]

Is it normal practice to always have a comment and then a cy.step("") with a string that says the same thing as the comment? Or is it just because the test was written without cy.step initially and the comments are leftovers?

[antowaddle]

I've intentionally left comments also, in some more intricate tests we may also want to add comments but not necessarily print that information to the console in cy.step.