-
Notifications
You must be signed in to change notification settings - Fork 49
Add E2E test workflow with Playwright in CI #555
Copy link
Copy link
Open
Labels
GrantFox OSSIssue tracked in GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardIssue may be eligible for a GrantFox rewardThird CampaignCampaign: Third CampaignCampaign: Third CampaigndevopsIssues related to infrastructure, CI/CD, and deploymentIssues related to infrastructure, CI/CD, and deploymentmediumModerate tasksModerate tasks
Description
Activity
Metadata
Metadata
Assignees
Labels
GrantFox OSSIssue tracked in GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardIssue may be eligible for a GrantFox rewardThird CampaignCampaign: Third CampaignCampaign: Third CampaigndevopsIssues related to infrastructure, CI/CD, and deploymentIssues related to infrastructure, CI/CD, and deploymentmediumModerate tasksModerate tasks
What
e2e.ymlworkflow exists and Playwright is configured but needs proper CI integration with backend + frontend services.Why
E2E tests catch integration issues between frontend and backend that unit tests miss. Currently not enforced.
Scope
In scope: CI starts backend + frontend, runs Playwright, uploads report as artifact
Out of scope: Visual regression, cross-browser matrix
Acceptance Criteria
Technical Context
.github/workflows/e2e.yml— existing workflowfrontend/playwright.config.ts— Playwright configfrontend/e2e/— 5 test files