CI: Implement Automated Unit and End-to-End Testing Workflows

[arii]

Original Issue Body

Description

Currently, jest and playwright tests are not running in CI.

Task

1. Modify pr-quality-standalone.yml (or create ci.yml).
2. Add a step to run unit tests: pnpm test.
3. Add a step to run E2E tests if applicable.
4. Ensure deploy.yml requires the test job to pass before executing deployment.

---

Auto-generated via RepoAuditor CI Health Analysis.

Original Issue

---

Title: ci: enable automated unit and E2E testing in workflows
Body:

Description

Currently, jest and playwright tests are not running in CI.

Task

1. Modify pr-quality-standalone.yml (or create ci.yml).
2. Add a step to run unit tests: pnpm test.
3. Add a step to run E2E tests if applicable.
4. Ensure deploy.yml requires the test job to pass before executing deployment.

---

Auto-generated via RepoAuditor CI Health Analysis.

Refined Description

Automated testing is a critical component of our CI/CD pipeline, ensuring code quality and preventing regressions. Currently, our continuous integration workflows are not executing jest for unit tests and playwright for end-to-end (E2E) and visual regression tests.

Proposed Changes

To address this, the following steps are required:

1. Workflow Configuration: Update the existing pr-quality-standalone.yml workflow, or create a new dedicated ci.yml workflow, to manage automated testing jobs.
2. Unit Test Integration: Add a specific step to run unit tests using the pnpm test command. This will execute all configured jest tests within the CI environment.
3. E2E Test Integration: Integrate end-to-end and visual regression tests. As per the project features, Playwright is used for screenshot-based testing, so this step should execute the relevant Playwright test command (e.g., pnpm test:e2e or similar).
4. Deployment Gate: Establish a dependency in deploy.yml to ensure that the deployment workflow only proceeds if all automated test jobs (unit and E2E) have successfully passed. This will act as a crucial quality gate for releases.

Rationale

Implementing these automated tests in CI will significantly improve the reliability and stability of our releases, align with our 'Production Readiness Focus,' and help detect issues early in the development cycle, reducing the risk of critical bugs reaching production.

[arii]

🤖 Gemini Smart Triage

Summary: Implement automated unit and end-to-end (E2E) testing within the CI/CD pipeline to ensure code quality and prevent regressions before deployment.
Priority: High | Score: 9/10

Analysis:
The issue correctly identifies a critical gap in the project's CI/CD pipeline: the absence of automated unit and E2E test execution. Integrating jest for unit tests and playwright for E2E/visual regression tests (as specified in project features) into the CI workflow is essential for maintaining code quality, preventing regressions, and supporting the 'Production Readiness Focus'. The task clearly outlines the necessary steps, including modifying existing workflow files and establishing a deployment gate. This is a high-priority task as it directly impacts product stability and development efficiency.

Suggestion: Consider renaming this issue to: "CI: Implement Automated Unit and End-to-End Testing Workflows"

[google-labs-jules]

Jules is on it. When finished, you will see another comment and be able to review a PR.

[google-labs-jules]

Ready for a review! A PR has been created.