Cypress e2e Test - Verifies users can create, edit and delete a Persistent Volume

[antowaddle]

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

Description

• Migrate 'Verifies users can create/delete a PersistentVolume' to Cypress ODS-1824
  -This test focuses on PVC management through the user interface (UI). It encompasses the following key steps and verifications:

1. PVC Creation: Initiates the process by creating a new Persistent Volume Claim via the UI.
2. Dashboard Configuration Check: Verifies the PVC value in the dashboard configuration to ensure it matches the expected settings.
3. UI Consistency Verification: Compares the dashboard configuration PVC value with the corresponding value displayed on the UI, ensuring consistency across the system.
4. PVC Editing: Incorporates functionality to edit the existing PVC, allowing for testing of modification capabilities.
5. PVC Deletion: Concludes by deleting the created PVC, testing the complete lifecycle of a Persistent Volume Claim.

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
• Locally against a PSI cluster and ODH-Nightly
  

Test Impact

• None - this is a test

How to run?
Go to odh-dashboard/frontend/src/tests/cypress and run the command npx cypress open . This will open the Cypress UI where testClusterStorageCreation.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/clusterStorage/testClusterStorageCreation.cy.ts" --browser chrome

or Execute 'npx cypress run --env grepTags=@ODS-1824'

Request review criteria:

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)

If you have UI changes:

• Included any necessary screenshots or gifs if it was a UI change.
• Included tags to the UX team if it was a UI/UX change.

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.14%. Comparing base (3167270) to head (2535e00).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3689      +/-   ##
==========================================
- Coverage   84.16%   84.14%   -0.03%     
==========================================
  Files        1453     1453              
  Lines       33865    33865              
  Branches     9384     9384              
==========================================
- Hits        28504    28496       -8     
- Misses       5361     5369       +8     

see 7 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 3167270...2535e00. Read the comment docs.

[ConorOM1]

@antowaddle maybe we could include editing also ? Or have we a separate test for this ?

[ConorOM1]

the PR description mentions data connections ? This is for PV storage right ?

[antowaddle]

the PR description mentions data connections ? This is for PV storage right ?

@ConorOM1 Yes, good spot. Amended now.

[antowaddle]

@antowaddle maybe we could include editing also ? Or have we a separate test for this ?

@ConorOM1 I'm not sure if we have a specific test case for this, but I've added it to this test.

[ConorOM1]

nice work @antowaddle !

[ConorOM1]

/lgtm

[manosnoam]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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/src/tests/OWNERS [manosnoam]

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