-
Notifications
You must be signed in to change notification settings - Fork 0
Setup Playwright testing with CI workflow #19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: shenanigansd <54628770+shenanigansd@users.noreply.github.com>
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
dotforge | 465f52a | Commit Preview URL Branch Preview URL |
Jan 15 2026, 05:55 AM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR sets up Playwright as an end-to-end testing framework for the DotForge web application with an automated CI workflow. The implementation adds testing infrastructure and configuration along with basic smoke tests to verify the application loads correctly.
Changes:
- Added Playwright as a dev dependency with test scripts in package.json
- Created Playwright configuration with multi-browser support (Chromium, Firefox, WebKit)
- Added two basic E2E tests to verify homepage loads and the ArtboardEditor component is present
- Created GitHub Actions workflow to run Playwright tests on CI
- Updated .gitignore to exclude Playwright test artifacts
Reviewed changes
Copilot reviewed 4 out of 6 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| package.json | Added Playwright dependency and test scripts (test, test:ui, test:headed) |
| package-lock.json | Lock file updates for Playwright and its dependencies |
| playwright.config.ts | Playwright configuration with dev server setup and multi-browser testing |
| tests/homepage.spec.ts | Basic E2E tests for homepage loading and component visibility |
| .gitignore | Added Playwright artifact directories to ignore list |
| .github/workflows/playwright.yaml | CI workflow for running Playwright tests on push and PRs |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: Bradley Reynolds <bradley.reynolds@tailstory.dev>
Signed-off-by: Bradley Reynolds <bradley.reynolds@tailstory.dev>
Signed-off-by: Bradley Reynolds <bradley.reynolds@tailstory.dev>
Signed-off-by: Bradley Reynolds <bradley.reynolds@tailstory.dev>
Adds E2E testing infrastructure using Playwright with automated CI execution.
Changes
@playwright/testwith configuration for Chromium, Firefox, and WebKitnpm run test,test:ui, andtest:headedscriptsExample test structure:
The CI workflow uses
npx playwright install --with-depsto ensure all browser engines are available in the pipeline.Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
https://storage.googleapis.com/chrome-for-testing-public/143.0.7499.4/linux64/chrome-headless-shell-linux64.zip/usr/local/bin/node /usr/local/bin/node /home/REDACTED/work/dotforge-web/dotforge-web/node_modules/playwright-core/lib/server/registry/oopDownloadBrowserMain.js(http block)https://storage.googleapis.com/chrome-for-testing-public/143.0.7499.4/linux64/chrome-linux64.zip/usr/local/bin/node /usr/local/bin/node /home/REDACTED/work/dotforge-web/dotforge-web/node_modules/playwright-core/lib/server/registry/oopDownloadBrowserMain.js(http block)telemetry.astro.build/usr/local/bin/node node /home/REDACTED/work/dotforge-web/dotforge-web/node_modules/.bin/astro build(dns block)/usr/local/bin/node node /home/REDACTED/work/dotforge-web/dotforge-web/node_modules/.bin/astro dev(dns block)workers.cloudflare.com/usr/local/bin/node node /home/REDACTED/work/dotforge-web/dotforge-web/node_modules/.bin/astro dev(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.