test: Cypress - Verify users can create a workbench and connect an existent PersistentVolume

[FedeAlonso]

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

Description

Smoke migration from ODS-CI
Test: ODS-1814 : Verify User Can Create And Start A Workbench With Existent PV Storage

How Has This Been Tested?

Using a RHOAI 2.16 operator
Command: npx cypress run --spec "cypress/tests/e2e/dataScienceProjects/workbenches" --browser chrome

Test Impact

It's a new e2e 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

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.32%. Comparing base (1fe5c73) to head (4b34981).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3511   +/-   ##
=======================================
  Coverage   85.31%   85.32%           
=======================================
  Files        1354     1354           
  Lines       31110    31110           
  Branches     8687     8687           
=======================================
+ Hits        26543    26544    +1     
+ Misses       4567     4566    -1     

see 4 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 1fe5c73...4b34981. Read the comment docs.

[antowaddle]

Can we reference these values also from the fixtures file?

[FedeAlonso]

Hmmm... I don't really understand what do you mean here.
notebookRow is an object, which gets selected dinamically

[manosnoam]

@antowaddle if you meant 's2i-minimal-notebook' - it comes from the Dashboard UI, not from test data, so there's no need to add it to fixtures.

[antowaddle]

Sorry, my comment wasn't clear. I was referring to the values below.

notebookRow.expectStatusLabelToBe('Running', 120000);
notebookRow.shouldHaveNotebookImageName('Minimal Python');
notebookRow.shouldHaveContainerSize('Small');

[manosnoam]

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

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

[manosnoam]

@FedeAlonso I tried it on dashobard-e2e cluster, and it failed on:
AssertionError: Timed out retrying after 10000ms: Unable to find an element by: [data-testid="s2i-minimal-notebook"]