-
Story
-
Resolution: Done
-
Major
-
None
-
None
As a developer, I want to go through the e2e tests and remove PatternFly classnames being used as selectors so that future PatternFly upgrades do not break integration tests.
AC:
- discover which e2e tests exist that call out PatternFly classnames as selectors (search for '.pf')
- remove any PatternFly classnames from `frontend/packages/integration-tests-cypress` and `frontend/packages/operator-lifecycle-manager/integration-tests-cypress`
- clones
-
CONSOLE-3826 Remove class name selectors from integration tests
- Closed
- is cloned by
-
ODC-7431 Remove PatternFly classname selectors from dev-console integration tests
- Closed
- links to