test(e2e): make context-menu delete-confirm spec fail-closed #2801
Reference in New Issue
Block a user
Delete Branch "fix/2798-context-menu-delete-false-green"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Closes #2798. Follow-up fix for #2805.
The suite-level
beforeEachskipped the file when/workspaceswas empty, so the primary delete-confirm test silently skipped instead of running. The initial fix added a global empty-canvas precondition, but Researcher noted that over-constrained shared/seeded E2E platforms (#2805).seedWorkspacehelper so each test creates and registers its own leaf workspace.E2E Delete Testnode by name and can run alongside pre-existing workspaces.test.skip()paths remain, and the seeded node must appear before the context-menu interaction.Test plan
npx eslint e2e/context-menu-delete.spec.tspasses.@playwright/testversion issue in this workspace; the change is a straightforward setup refactor and will be validated by the existingcontext-menu-deleteE2E gate in CI.Fixes #2798
Closes #2805
🤖 Generated with Claude Code
APPROVED on head
da45b2b84f.This resolves my #2798 RCA cleanly. The suite-level empty-workspace skip is gone, both tests seed/register their own workspace through
seedWorkspace, and the delete-confirm path now fails closed instead of silently skipping when/workspacesstarts empty. The delete test also asserts the initially empty workspace list before seeding, so the old false-green class is directly covered rather than only avoided incidentally.5-axis check:
test.skipremains in this spec; cancel path also seeds its own fixture.CI / all-requiredare green on this head.No findings.
APPROVED on head
da45b2b8.Tests-only 5-axis review:
No findings.