Skip to content

test: Add CI smoke tests for Docker, Electron, and Web#349

Open
icebear0828 wants to merge 1 commit intomasterfrom
ci-smoke-tests-9084205728708085973
Open

test: Add CI smoke tests for Docker, Electron, and Web#349
icebear0828 wants to merge 1 commit intomasterfrom
ci-smoke-tests-9084205728708085973

Conversation

@icebear0828
Copy link
Copy Markdown
Owner

This commit addresses #133, #134, and #135 by implementing independent CI smoke tests for each of the core components of the Codex Proxy application.

  1. Docker: A workflow builds the image and checks its default and custom port behavior through port mapping + mounted config overlays, verifying the healthcheck status and endpoint response.
  2. Electron: Playwright dependencies were added to the electron workspace, along with a smoke.test.ts that relies on xvfb and an unpacked application to assert basic window-launch behavior. A CI workflow handles the full build, prepare, unpack, and launch sequence.
  3. Web: A new vitest file in src/__tests__/ validates Tailwind's CSS compilation (checking for color-scheme properties from dark mode plugin classes) and ensures the built Hono Node server can host the index.html payload appropriately on an arbitrary port.

PR created automatically by Jules for task 9084205728708085973 started by @icebear0828

- Added GitHub Actions workflow `docker-smoke-test.yml` for container validation.
- Added GitHub Actions workflow `electron-smoke-test.yml` and Playwright launch test `smoke.test.ts` for Electron application validation.
- Added GitHub Actions workflow `web-smoke-test.yml` and Vitest server validation test `web-smoke.test.ts` for frontend compilation/serving validation.
- Updated `packages/electron/package.json` to include Playwright devDependencies.

Co-authored-by: icebear0828 <[email protected]>
@google-labs-jules
Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

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