Cypress e2e Test - Verify User Can Access Jupyter Launcher From DS Project Page

[ConorOM1]

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

Description

Migrate ODS-1877 to Cypress with additional enhancements added

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

• Tested against ODH-Nightly & RHOAI nightly

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 testLaunchStandaloneNotebook.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/testLaunchStandaloneNotebook.cy.ts" --browser chrome

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

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

[openshift-ci]

Hi @ConorOM1. Thanks for your PR.

I'm waiting for a opendatahub-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[manosnoam]

/lgtm

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

New changes are detected. LGTM label has been removed.

[manosnoam]

/approve

[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

[antowaddle]

Great work Conor, I've added some minor comments.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.16%. Comparing base (793bdb7) to head (5311b8a).
Report is 28 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3553      +/-   ##
==========================================
- Coverage   85.57%   85.16%   -0.41%     
==========================================
  Files        1371     1380       +9     
  Lines       31180    31542     +362     
  Branches     8727     8818      +91     
==========================================
+ Hits        26681    26863     +182     
- Misses       4499     4679     +180     

Files with missing lines	Coverage Δ
...otebookController/screens/server/ImageVersions.tsx	93.75% <ø> (ø)

... and 304 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 793bdb7...5311b8a. Read the comment docs.

[antowaddle]

@ConorOM1 thanks for the latest changes, some good improvements. Can you check please check this also by running the test in Jenkins along with the other current tests? There is a step that opens a new tab which I've seen running the tests locally physically opened a new tab, we need to ensure that there are no unintended consequences of doing this to other tests.

[ConorOM1]

@ConorOM1 thanks for the latest changes, some good improvements. Can you check please check this also by running the test in Jenkins along with the other current tests? There is a step that opens a new tab which I've seen running the tests locally physically opened a new tab, we need to ensure that there are no unintended consequences of doing this to other tests.

@antowaddle tested in Jenkins, looks good, no effect on other tests, videos, screenshots etc. Here: cypress/job/dashboard-tests/143/Test_20Reports/

[antowaddle]

/lgtm /approve