Milestones

List view

• Initial PW framework setup

  Stand up the WCC QA test automation framework from scratch so the team has a reliable, type-safe foundation for both API and UI testing, with quality gates and CI in place. This epic covers the end-to-end groundwork: the API testing layer, the admin portal UI testing layer, code-quality tooling (linter + formatter), and continuous integration. By the end, any contributor can clone the repo, configure credentials, and run a green test suite locally and on CI.

  Due by September 30, 2026

  •4/5 issues closed
  80% complete1 open4 closed

• Open-source readiness

  Summary: make wcc-qa welcoming to external contributors. The codebase already has a strong technical foundation (README, Apache 2.0 license, ESLint/Prettier/Husky, type-safe Faker+Zod API layer). The gaps are governance and automation, not code quality, no .github/, no CI, no contributor guides. Outcome: a newcomer can, in minutes, understand the project, find a good-first-issue, know how to open a PR, and get automated fast feedback (lint/typecheck) — with clear community standards and maintainer ownership.

  Due by September 30, 2026

  •4/12 issues closed
  33% complete8 open4 closed