Skip to content

Add Electron smoke test and CI workflow#343

Open
icebear0828 wants to merge 1 commit intomasterfrom
feat/electron-smoke-test-10685046239386491693
Open

Add Electron smoke test and CI workflow#343
icebear0828 wants to merge 1 commit intomasterfrom
feat/electron-smoke-test-10685046239386491693

Conversation

@icebear0828
Copy link
Copy Markdown
Owner

This commit addresses the issue to verify that the Electron application builds and launches without crashing.
It sets up a Playwright-driven test that spins up the Electron executable, confirms that it opens, and verifies that the main window has the expected "Codex Proxy Developer Dashboard" title.
It also introduces a comprehensive GitHub Actions CI pipeline ci-electron.yml to compile the TypeScript, bundle the web and node layers, build the Rust native addon, package the application for Linux using electron-builder, and verify the app's startup headless via xvfb.


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

- Add playwright and @playwright/test to packages/electron/package.json
- Add a launch-smoke.test.ts testing basic electron main window creation using playwright
- Add 'test' script running vitest in packages/electron/package.json
- Add a new GitHub Actions workflow ci-electron.yml to run tests for Electron on master using xvfb

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