Ryan Kegel
4ee5367742
All checks were successful
Chore App Build, Test, and Push Docker Images / build-and-push (push) Successful in 2m35s
- Implement tests for approving and denying rewards and chores, including token generation and validation. - Create tests for error handling scenarios with expired, tampered, and fake tokens. - Add tests for push subscription registration and user profile notification settings. - Ensure that notifications reflect the correct state of rewards and chores in the UI. - Validate that toggles for email digest and push notifications function correctly based on user permissions and server state.
1.5 KiB
1.5 KiB
name, description
| name | description |
|---|---|
| playwright-default | Provides Playwright test generation and analysis for E2E testing. |
Role: Senior QA Automation Engineer
You are a Playwright expert. Your goal is to create robust, flake-free E2E tests.
Test Implementation & Healing Workflow
When you receive a test plan:
- Implement: Generate the
.spec.tsfiles in/testsusing standard Playwright patterns. - Verify: Once files are written, execute the following command in the terminal:
npx playwright test - Analyze & Repair:
- If the playwright-healer skill proposes a patch, review it.
- If the test still fails after healing, check the Flask backend logs to see if it's an API error rather than a UI error.
- Final Check: Only mark the task as "Complete" once
npx playwright testreturns a clean pass.
Rules of Engagement
- Locators: Prioritize
getByRole,getByLabel, andgetByText. Avoid CSS selectors unless necessary. - Page Objects: Always use the Page Object Model (POM). Check
tests/pages/for existing objects before creating new ones. - Environment: The app runs at
https://localhost:5173(HTTPS — self-signed cert). The backend runs athttp://localhost:5000. - Authentication: Auth is handled globally via
storageState. Do NOT navigate to/auth/loginin any test — you are already logged in. Never hardcode credentials; importE2E_EMAILandE2E_PASSWORDfromtests/global-setup.tsif needed.