Skip to content

Make the EE Cypress specs independent of run order #9005

Open

Description

@andypalmi

Same problem as the OS suite: the EE specs pass only in the default order.

Specs that fail out of order:

  • applications/applications.spec.js (Cannot read properties of undefined (reading 'id'))
  • applications/device-groups.spec.js
  • devices/developer-mode.spec.js (cy.click() blocked by a dialog overlay that is still open). Also failed on CI in Flaky backend tests: billing trial state, 3rd party broker topics, device APIs #8478, with the same error.
  • rbac/rbac-owner-contextual.spec.js (dashboard counts and tile counts differ: found 4 or 5, expected 3)

Done when

  • Each spec creates the data it needs or restores what it changes in after().
  • The suite passes run alphabetically and when split into 2 or 3 groups with --spec.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions