Skip to content

Plan: QA Test Cases App

Proposal for a new Angular web app within the Syncc monorepo for test case management, aimed at the QA team and non-technical staff.

Context

  • The team has an official QA member and non-technical collaborators.
  • Test cases are currently managed in Notion.
  • Syncc runs on a self-hosted server — no external hosting dependency.
  • Goal: migrate QA management to a tool integrated with the Syncc backend.

Pros

Natural integration with the backend Endpoints, DTOs, and the Prisma schema already exist. The app can generate test cases pre-populated with real data (routes, drivers, vehicles) without hardcoding fixtures.

Monorepo = immediate reuse Shared TypeScript types, same environment.ts, same CI pipeline. No separate repo or duplicated configuration needed.

Progressive automation Start by writing cases manually. Those same DB records become the source of truth for automated tests in a later phase.

Centralizes coverage A dashboard showing which features have written test cases and which don't is genuinely useful for a team that can't cover everything at once.

Accessible to non-technical users A web interface is more approachable than YAML/JSON files or a GitHub repo for QA profiles and non-technical collaborators.

Cons / Risks

New app = new maintenance debt This would be the fourth Angular app in the monorepo. It requires its own deploy, updates, and ongoing attention.

Coupling with the backend Test cases should be queryable even if the backend is on a different version or down. The coupling needs to be designed carefully.

External integrations are out of scope for v1 Tools like SonarQube are built for enterprise-scale static analysis. Adding them in v1 introduces complexity with little immediate return.

Feature Description
Test Case CRUD Title, description, steps, expected result
Entity linking Associate cases with lines, drivers, vehicles, etc.
Manual execution status Passed / Failed / Blocked / Pending
Coverage dashboard Per-module view: how many cases exist and their current status
Authentication Reuse existing backend auth (roles: SUPER_ADMIN / QA)

Out of scope for v1

  • SonarQube or other external tool integrations → v2
  • Automated test execution → v3
  • Exportable reports (PDF/Excel) → v2

Critical condition

This development must not block or delay active features of the main product (drivers, passengers, admin). It must run as parallel work with separate capacity.

Next steps

  1. Confirm capacity availability for the following month without impacting the main roadmap.
  2. Technical planning session: define required backend routes, app structure within the monorepo, and data model.
  3. Create the apps/qa-portal app in the monorepo.
  4. Implement v1 in 1-week iterations.

Document generated: 2026-07-07