plantocode-live-e2e

To run live E2E tests with Auth0 JWT authentication, execute a test suite against a real runtime environment to validate actual authentication paths instead of relying on mocks, capturing desktop logs and artifacts for any failures.

Debugging refresh token validation in a desktop E2E environment involves running tests against a live runtime while directly monitoring PTY and log streams, allowing you to capture failure artifacts and analyze real authentication behavior.

Yes, you can validate Codex auth-file interactions without mocks by running live end-to-end tests that verify real authentication paths, including Auth0-backed JWT checks and refresh token verification.

Capturing desktop logs and failure artifacts during end-to-end testing requires running live E2E tests against a real runtime environment, automatically collecting logs and artifacts for detailed analysis and remediation upon test failures.

Direct PTY and log stream monitoring is required during live E2E test execution to observe real-time authentication behavior and operational paths, ensuring accurate debugging of JWT checks and token validation without mock interference.

Live E2E testing should be used instead of mocked tests when validating critical user authentication or voice transcription features, ensuring comprehensive end-to-end validation against a staging or production-like environment to catch regressions before release.