feat(e2e): add Playwright post submission test (E2E-POST-001)

[niamao]

Summary

• Adds Playwright E2E infrastructure for the frontend (e2e/, playwright.config.ts, flexible pnpm test:e2e scripts)
• Implements E2E-POST-001: logged-in user creates a public post via the composer, verifies explore feed and post detail page (desktop + mobile)
• Fixes REST login to support hosted API (/login) and local backend (/auth/login) via shared restLogin helper
• Adds UI data-testids, combobox z-index fix for group selection in the Create Quote dialog, and excludes e2e/ from Jest so CI unit tests stay isolated
• Documents setup in README.md, CLAUDE.md, and .env.e2e.example; adds optional CI E2E job when E2E_AUTHOR_PASSWORD is configured

Test plan

• pnpm type-check
• pnpm lint
• pnpm build
• pnpm test (Jest — 155 suites)
• pnpm test:e2e post-submission.spec.ts (2 passed: desktop + mobile)
• CI E2E job (requires repo secrets: E2E_AUTHOR_PASSWORD, optional E2E_AUTHOR_USERNAME, E2E_PUBLIC_GROUP_NAME)

Made with Cursor

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
quotevote	Ready	Preview, Comment	Jul 6, 2026 1:53am

[flyblackbox]

I am sorry for the delay @niamao we need to find a new system for reviews instead of relying on one person. Please give me some time and I will find a volunteer who can do review. In the meantime, may I ask that you review someone else's PR?

[motirebuma]

Hey @niamao the E2E infrastructure and test spec look solid, good global setup, clean helper abstractions, and the restLogin.ts fallback for hosted vs local backends is a nice touch. Docs and config are thorough.

A couple things to sort out before merging:

• The CI job gate if: ${{ secrets.E2E_AUTHOR_PASSWORD }} likely won't work as intended -- GitHub Actions masks secrets in if: expressions. You'll want to set the secret into an env var and check that instead, otherwise this job may silently always skip.
• There's some scope creep here: the GET_GROUP query + group badge in Post.tsx and the z-index: 80 bump on the combobox popover aren't related to E2E setup.
• Minor: saveAuthorStorageState launches a full Chromium instance just to write localStorage. A plain JSON file with cookies/origins would be faster and skip the browser roundtrip, but not a blocker.

Status: Approved (Will be merged after the fixes)

Thankyou @niamao, and sorry for late review.

@niamao @flyblackbox

[niamao]

I am sorry for the delay @niamao we need to find a new system for reviews instead of relying on one person. Please give me some time and I will find a volunteer who can do review. In the meantime, may I ask that you review someone else's PR?

Currently, the remaining PRs still have build errors and it's better if they can fix it first.

[niamao]

Hey @niamao the E2E infrastructure and test spec look solid, good global setup, clean helper abstractions, and the restLogin.ts fallback for hosted vs local backends is a nice touch. Docs and config are thorough.

A couple things to sort out before merging:

• The CI job gate if: ${{ secrets.E2E_AUTHOR_PASSWORD }} likely won't work as intended -- GitHub Actions masks secrets in if: expressions. You'll want to set the secret into an env var and check that instead, otherwise this job may silently always skip.
• There's some scope creep here: the GET_GROUP query + group badge in Post.tsx and the z-index: 80 bump on the combobox popover aren't related to E2E setup.
• Minor: saveAuthorStorageState launches a full Chromium instance just to write localStorage. A plain JSON file with cookies/origins would be faster and skip the browser roundtrip, but not a blocker.

Status: Approved (Will be merged after the fixes)

Thankyou @niamao, and sorry for late review.

@niamao @flyblackbox

No problem. Thank you also for reviewing. I'll update my changes and also fix merge conflicts.

[flyblackbox]

Looking good to me

[niamao]

Looking good to me

I wanted to check and fix my deployment error but I don't have access permission. @flyblackbox @motirebuma

[flyblackbox]

I'm not sure how to address this one @niamao / @motirebuma I will message you

[niamao]

Hey @niamao the E2E infrastructure and test spec look solid, good global setup, clean helper abstractions, and the restLogin.ts fallback for hosted vs local backends is a nice touch. Docs and config are thorough.

A couple things to sort out before merging:

• The CI job gate if: ${{ secrets.E2E_AUTHOR_PASSWORD }} likely won't work as intended -- GitHub Actions masks secrets in if: expressions. You'll want to set the secret into an env var and check that instead, otherwise this job may silently always skip.
• There's some scope creep here: the GET_GROUP query + group badge in Post.tsx and the z-index: 80 bump on the combobox popover aren't related to E2E setup.
• Minor: saveAuthorStorageState launches a full Chromium instance just to write localStorage. A plain JSON file with cookies/origins would be faster and skip the browser roundtrip, but not a blocker.

Status: Approved (Will be merged after the fixes)

Thankyou @niamao, and sorry for late review.

@niamao @flyblackbox

Thanks for the review — addressed: (1) CI gate now checks E2E_AUTHOR_PASSWORD via step env + output, not if: secrets.*; (2) reverted Post.tsx scope creep; (3) kept combobox z-[80] because group select is blocked in E2E without it; (4) storage state is plain JSON, no Chromium launch.

E2E runs in CI once E2E_AUTHOR_PASSWORD is set in repo Actions secrets. (Optional) @motirebuma @flyblackbox

[motirebuma]

Nice work @niamao. The E2E infrastructure is solid -- good global setup, clean helper abstractions, and the restLogin.ts fallback for hosted vs local backends is a nice touch. Docs and config are thorough.

• Minor: saveAuthorStorageState launches a full Chromium instance just to write localStorage. A plain JSON file with cookies/origins would be faster, but not a blocker.

Thank you!!

@flyblackbox @niamao