Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix namespace-picker.spec.ts e2e test failing in 2.10 #12338

Open
momesgin opened this issue Oct 23, 2024 · 1 comment · May be fixed by #12362
Open

Fix namespace-picker.spec.ts e2e test failing in 2.10 #12338

momesgin opened this issue Oct 23, 2024 · 1 comment · May be fixed by #12362
Assignees
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@momesgin
Copy link
Member

Setup

  • Rancher version: 2.10
  • Rancher UI Extensions:
  • Browser type & version:

Describe the bug

After updating our e2e test env pointing to the latest backend(2.10) a test from namespace-picker.spec.ts fails.

Test case:
newly created project/namespace appears in namespace picker

Path:
cypress/e2e/tests/pages/explorer2/namespace-picker.spec.ts

Additional context

The PR to update e2e test env to point to the latest backend.

@momesgin momesgin added this to the v2.10.0 milestone Oct 23, 2024
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Oct 23, 2024
@momesgin momesgin self-assigned this Oct 24, 2024
@momesgin momesgin linked a pull request Oct 24, 2024 that will close this issue
7 tasks
@gaktive
Copy link
Member

gaktive commented Oct 30, 2024

Blocked on #12406 so once that's resolved, let's see how this looks.

@nwmac nwmac modified the milestones: v2.10.0, v2.11.0 Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants