Skip to content

test(e2e): add EPIC-08 document integration E2E test coverage#382

Merged
steilerDev merged 2 commits into
betafrom
chore/8-refinement
Mar 2, 2026
Merged

test(e2e): add EPIC-08 document integration E2E test coverage#382
steilerDev merged 2 commits into
betafrom
chore/8-refinement

Conversation

@steilerDev
Copy link
Copy Markdown
Owner

Summary

  • Updates DocumentsPage POM from the old stub version to the full EPIC-08 implementation, adding locators for the DocumentBrowser "not configured" state
  • Removes the Documents page loads with heading test from stub-pages.spec.ts since the Documents page has graduated to a full feature page (EPIC-08)
  • Adds e2e/tests/documents/documents-browser.spec.ts with 8 scenarios covering the Documents page: page load smoke, "not configured" state rendering, env var instructions, navigation/deep-linking, responsive layout, dark mode, accessibility (h1/h2 heading structure), and Paperless status API
  • Adds e2e/tests/documents/documents-linked-sections.spec.ts with 10 scenarios covering the LinkedDocumentsSection component on work item detail (6 scenarios) and invoice detail (4 scenarios): section heading visibility, disabled add button when not configured, not-configured banner text, aria-labelledby accessibility, responsive no-scroll layout, and dark mode

All tests validate against the "not configured" state since PAPERLESS_URL and PAPERLESS_API_TOKEN are not set in the E2E testcontainer environment. This is the correct approach per the E2E test setup — Paperless availability cannot be assumed in the automated test environment.

Test plan

  • CI E2E smoke tests pass (desktop/Chromium)
  • Full E2E test matrix passes (desktop, tablet, mobile viewports)
  • documents-browser.spec.ts: Documents page shows "Paperless-ngx Not Configured" heading
  • documents-browser.spec.ts: API /api/paperless/status returns configured: false
  • documents-linked-sections.spec.ts: Work item detail page shows Documents section with disabled Add button
  • documents-linked-sections.spec.ts: Invoice detail page shows Documents section with disabled Add button

Closes #360 (E2E validation portion)

🤖 Generated with Claude Code

claude added 2 commits March 2, 2026 21:31
- Update DocumentsPage POM from stub to full implementation with locators
  for the DocumentBrowser "not configured" state
- Remove Documents test from stub-pages.spec.ts (page graduated to full
  feature in EPIC-08)
- Add e2e/tests/documents/documents-browser.spec.ts covering 8 scenarios:
  page load smoke, not-configured state rendering, env var instructions,
  navigation, responsive layout, dark mode, accessibility, and API status
- Add e2e/tests/documents/documents-linked-sections.spec.ts covering 10
  scenarios: LinkedDocumentsSection on work item detail (6) and invoice
  detail (4) — heading visibility, disabled add button, not-configured
  banner, aria-labelledby, responsive layout, dark mode

All tests validate against the "not configured" state since PAPERLESS_URL
and PAPERLESS_API_TOKEN are not set in the E2E testcontainer environment.

Fixes #360

Co-Authored-By: Claude qa-integration-tester (Sonnet 4.5) <noreply@anthropic.com>
Records DocumentBrowser state machine, LinkedDocumentsSection selectors,
invoice detail route URL pattern, and Paperless API endpoints for future
test sessions.

Co-Authored-By: Claude qa-integration-tester (Sonnet 4.5) <noreply@anthropic.com>
@steilerDev steilerDev merged commit 390032e into beta Mar 2, 2026
9 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Mar 2, 2026

🎉 This PR is included in version 1.10.0-beta.83 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Mar 2, 2026

🎉 This PR is included in version 1.11.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants