Testing & Release Process

---

QA Workflow Agreement

1. When does testing start?

Testing begins when:

• the developer has finished work on the task,
• the code has passed Code Review,
• the feature is deployed to the staging environment,
• the task is moved to the Ready for QA status.

👉 Trigger: the task appears on the Kanban board in Ready for QA / Ready for Testing (In Review) → In Testing → Ready for Production → Done.

---

2. What data is required for testing?

For proper verification, QA needs:

• feature description / acceptance criteria (expected behavior),
• link to the staging environment,
• test accounts / test data,
• if there are API changes → Swagger or contract description,
• access to the database (if needed).

---

3. When is a feature ready for production release?

A feature can be released to production if:

• all test cases / checklists are passed,
• no critical or major bugs remain,
• key scenarios have passed basic regression (smoke test),
• the task is moved to the Ready for Release status.

---

4. How do we test on production?

After deployment to production, perform a smoke test:

• verify the new feature,
• verify core business flows (login, payments, search, etc.),
• monitor logs, alerts, analytics (Sentry, GA, Datadog, etc.),
• if a critical bug is found → perform immediate rollback or hotfix.

---

5. What else is needed for high-quality releases?

• QA checklist (minimum set of verifications for each release),
• Regression plan (short list of critical scenarios),
• Release notes (brief description of changes for the whole team).

Clear communication:

• Dev → QA: what has been done and where to test,
• QA → PM: release readiness status.

---