Francy51/Neon-Desk
2
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects Releases Wiki Activity

Research MVP e2e has duplicate accessible label for NVDA status selector #30

New Issue
Open
opened 2026-03-16 19:16:57 +00:00 by Francy51 · 0 comments
Francy51 commented 2026-03-16 19:16:57 +00:00
Owner
Copy Link

E2E run: bun run test:e2e on 2026-03-16

Failing spec:

  • e2e/research-mvp.spec.ts:156 supports the core coverage-to-research workflow

Observed behavior:

  • Playwright strict mode fails because getByLabel('NVDA status') resolves to two elements instead of one.

Failure excerpt:

  • strict mode violation: getByLabel('NVDA status') resolved to 2 elements
  • one under article and one under getByRole('cell', { name: 'Backlog' })

Artifacts:

  • output/playwright/test-results/research-mvp-supports-the-core-coverage-to-research-workflow/error-context.md
  • output/playwright/test-results/research-mvp-supports-the-core-coverage-to-research-workflow/test-failed-1.png
  • output/playwright/test-results/research-mvp-supports-the-core-coverage-to-research-workflow/trace.zip

This looks like an accessibility/DOM uniqueness regression rather than backend behavior.

E2E run: `bun run test:e2e` on 2026-03-16 Failing spec: - `e2e/research-mvp.spec.ts:156` `supports the core coverage-to-research workflow` Observed behavior: - Playwright strict mode fails because `getByLabel('NVDA status')` resolves to two elements instead of one. Failure excerpt: - strict mode violation: `getByLabel('NVDA status')` resolved to 2 elements - one under `article` and one under `getByRole('cell', { name: 'Backlog' })` Artifacts: - `output/playwright/test-results/research-mvp-supports-the-core-coverage-to-research-workflow/error-context.md` - `output/playwright/test-results/research-mvp-supports-the-core-coverage-to-research-workflow/test-failed-1.png` - `output/playwright/test-results/research-mvp-supports-the-core-coverage-to-research-workflow/trace.zip` This looks like an accessibility/DOM uniqueness regression rather than backend behavior.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0
Critical priority
 P1
High priority
 P2
Medium priority
 P3
Low priority
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
coolify_deployment Francy51
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Francy51/Neon-Desk#30
Delete Branch "%!s()"

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?