Skip to content

test(e2e): verify explicit previews and retain failure traces - #176

Open
anantham wants to merge 5 commits into
perf/codex-startup-latencyfrom
test/codex-production-qa
Open

test(e2e): verify explicit previews and retain failure traces#176
anantham wants to merge 5 commits into
perf/codex-startup-latencyfrom
test/codex-production-qa

Conversation

@anantham

@anantham anantham commented Sep 5, 2026

Copy link
Copy Markdown
Owner

Summary

The end-to-end runner could silently reuse a stale server, while a failed test with zero retries produced no trace. Reject occupied managed-server ports, allow an explicit LF_E2E_BASE_URL for a reviewed production preview, and retain traces on failure.

Changes

Update the existing Playwright configuration and QA guide. Document pinned setup, strict preview ports, isolated fresh/warm browser fixtures and trace inspection; remove stale schema and installation instructions. No additional orchestration layer or dependencies.

Testing

Node 24.19.0: three existing route tests pass against an explicit production preview; TypeScript and focused lint pass. An occupied-port probe proves the managed runner refuses a stale listener. A disposable intentional failure with zero retries produces trace.zip; the intentionally failing test is not part of the committed suite.

Review

Stacked on #173 for a focused diff. Production services and personal browser profiles were not modified.

Use the existing Playwright config for local production previews, refuse accidental dev-server reuse and retain traces without requiring a retry. Document locked setup and fresh/warm fixture boundaries.

Verification: three production route tests pass; occupied-port refusal and first-failure trace retention verified with temporary diagnostics. No dependencies or runtime behavior changed.
@vercel

vercel Bot commented Sep 5, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated
lexicon-forge Ready Ready Preview Sep 5, 2026 10:39am UTC

@anantham

anantham commented Sep 5, 2026

Copy link
Copy Markdown
Owner Author

@codex review Please review the current head and focused diff against #173. Existing production route checks pass through the explicit preview URL; a disposable probe verifies occupied-port rejection, and an intentional zero-retry failure produces a trace. No dependencies or runtime services were changed.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8e30c96e8f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread Issues.md Outdated
@anantham

anantham commented Sep 5, 2026

Copy link
Copy Markdown
Owner Author

Addressed the current-head review: QA-03 is explicitly partial and remains open for a scrubbed representative novel, fresh/warm session-harness checks, and a fixture/revision receipt. #176 only claims the tested runner and setup improvements. @codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e437faa735

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/infrastructure/E2E-TESTING.md Outdated
@anantham

anantham commented Sep 5, 2026

Copy link
Copy Markdown
Owner Author

The preview commands now use each worktree own ignored dist directory and require separate strict ports for concurrent previews. The guide also prohibits rebuilding that worktree while its tests run. No shared temporary output directory remains. QA-03 remains partial for representative novel/fresh-warm fixture acceptance. @codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: 0e695007d2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Preserve both worklog receipts and the partial QA acceptance status. QA implementation is unchanged; eight combined app-screen/dialog tests and TypeScript pass. Fresh CI and exact-head review follow.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant