You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ZEPPELIN-6358] Remove anti-patterns of E2E and tidy test suite
### What is this PR for?
Applied the [`e2e-reviewer`](https://github.com/dididy/e2e-skills) skill on the existing E2E suite. The skill does static analysis — it catches tests that can never actually fail, silent skips, swallowed errors in POM methods, that kind of thing.
Findings and fixes:
- `home-page-enhanced-functionality.spec.ts` was mostly duplicating `home-page-elements` and `home-page-note-operations` → deleted and merged
- `toBeGreaterThanOrEqual(0)` and `toBeAttached()` on static elements were always passing → replaced with assertions that can fail
- `if (isVisible) { expect() }` patterns silently skip when something breaks → removed or converted to `test.skip`
- Several POM methods had `.catch(() => {})` with no comment → removed; kept the intentional ones and marked with `// JUSTIFIED:`
- `document.querySelector` in `page.evaluate()` → swapped for Playwright locator API
- Added `aria-label` / `data-testid` to action bar HTML; a few tests were breaking on DOM structure changes
- Renamed a handful of tests whose names didn't match what they actually tested; dropped the ones that only called `toBeVisible()`
### What type of PR is it?
Improvement
Refactoring
### Todos
### What is the Jira issue?
ZEPPELIN-6358
### How should this be tested?
### Screenshots (if appropriate)
### Questions:
* Does the license files need to update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
Closes#5180 from dididy/tidy-e2e.
Signed-off-by: Jongyoul Lee <jongyoul@gmail.com>
0 commit comments