Update cypress libaries

[nwmac]

Up until recently, we have been using Sorry Cypress, which has limited us to an older version of cypress.

We're using 11.1.0 and the latest is 15.14.2.

I understand this is likely a breaking change, so we'll need to update something (tests and maybe config) to be able to use the latest library.

This ticket is about updating the main cypress library (and the other cypress libraries that we use) to bring us up to date now that we are no longer using Sorry Cypress.

I know moving from 11 > 12 requires the testIsolation to be updated to a boolean rather than on or off.

[github-actions]

🎯 Agentic Issue Triage

Summary: Tech-debt maintenance task to upgrade Cypress from 11.1.0 → 15.14.2. Previously blocked by Sorry Cypress (self-hosted Cypress Cloud alternative) requiring an older version. Now fully unblocked.

This is a significant major version jump (v11 → v15) spanning 4 major releases, requiring updates to config, tests, and supporting plugins.

---

📦 Packages to Audit & Update

Package	Current Version
cypress	11.1.0 → target 15.x
@cypress/grep	4.1.1
@cypress/vue	5.0.5
@cypress/webpack-dev-server	3.4.1
@cypress/code-coverage	3.10.4
@percy/cypress	3.1.6
cypress-axe	1.6.0
cypress-mochawesome-reporter	3.8.2
cypress-real-events	1.14.0
cypress-terminal-report	7.2.0
eslint-plugin-cypress	2.12.1 → upgrade to 3.x for Cypress 13+

⚠️ Key Breaking Changes (v11 → v15)

• v12: nodeVersion config removed; cy.session() caching behavior changed; Cypress.Blob helpers removed
• v13: experimentalSessionAndOrigin removed (now GA); cy.origin() always enabled; cy.intercept() async handler changes
• v14: TypeScript types tightened; Cypress.Commands.overwrite signature changes; component testing improvements
• v15: ESM module support improvements; review full changelog

Config file (cypress/base-config.ts): run cypress open after upgrade for config validation warnings.

References:

• (docs.cypress.io/redacted)
• (docs.cypress.io/redacted)

🔍 Upgrade Strategy

1. Upgrade incrementally (11→12→13→14→15) to isolate failures per version
2. Run the full test suite after each bump and fix failures before proceeding
3. Audit cypress/support/ (commands, index files) for breaking API changes
4. Ensure @cypress/vue version aligns with Cypress core (mismatches break component tests)
5. Upgrade eslint-plugin-cypress to 3.x early to avoid lint errors on new APIs

✅ Suggested Sub-Tasks

• Review all Cypress-related packages and identify latest compatible versions
• Upgrade cypress to 15.x (incremental approach recommended)
• Upgrade @cypress/vue and @cypress/webpack-dev-server to matching versions
• Upgrade eslint-plugin-cypress to 3.x
• Upgrade remaining plugins (axe, real-events, terminal-report, mochawesome-reporter, qase-reporter, percy)
• Audit and update cypress/base-config.ts for removed/renamed config keys
• Audit cypress/support/ for breaking API changes
• Run full E2E suite and fix broken tests
• Verify component tests pass with updated @cypress/vue
• Update TypeScript config under cypress/ if types changed

Note

🔒 Integrity filter blocked 1 item

The following item were blocked because they don't meet the GitHub integrity level.

• [UI] Investigation of how to dynamically change rancher prime theme #16699 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Agentic Triage for issue #17447 · ● 276.3K · ◷

[cnotv]

@nwmac could you brief me in about the current state of things regards the tests?

[nwmac]

The test state is good. Let me know what you need.

This should be a straight-forward dependency bump + updates for any breaking changes to the library - Claude or co-pilot should be able to take care of that.

Let me know what you need.