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
Two tests in `tests/e2e/basic-sortable.spec.ts` are skipped:
`tests/e2e/basic-sortable.spec.ts:93` — "shows hover effects on sortable items" — un-skipped during Tests: Un-skip and stabilize the deferred E2E specs #35 triage but FAILED with `transform` returning `'none'` even after `.hover()`. Hover-state CSS doesn't appear to apply the expected `translateY` transform on the `.sortable-item` selector in the demo fixture.
`tests/e2e/basic-sortable.spec.ts:107` — "handles touch input for drag and drop" — pointer-event-based touch simulation; touch path is partially covered by `on-move.spec.ts` but this specific test as written is flaky.
Failing assertion (hover effects)
```
expect(transform).not.toBe('none')
```
After `await item.hover()`, computed-style `transform` is still `'none'` — the CSS rule that the test expects to apply on hover isn't reaching the element. Likely the demo fixture's CSS no longer matches the test expectation.
Suggested approach
Audit the basic-list CSS in the demo (`index.html`) — confirm whether `.sortable-item:hover` is supposed to apply a transform. If not, this test is obsolete (consider deleting); if yes, restore the rule.
For the touch test, decide whether it's redundant with `on-move.spec.ts` pointer-pipeline coverage and delete, or rewrite to drive touch via the proper Playwright touchscreen API.
Problem
Two tests in `tests/e2e/basic-sortable.spec.ts` are skipped:
Failing assertion (hover effects)
```
expect(transform).not.toBe('none')
```
After `await item.hover()`, computed-style `transform` is still `'none'` — the CSS rule that the test expects to apply on hover isn't reaching the element. Likely the demo fixture's CSS no longer matches the test expectation.
Suggested approach
Refs #35 — discovered during E2E skip triage.