QA-03 — Functional test campaign — scripted scenarios on staging
Akram executes the scripted functional scenarios (per SRS acceptance criteria) on staging builds and files defects.
| Field | Details |
|---|---|
| Task code | QA-03 |
| Phase | P1 — V1 build & integration |
| Product scope | V1 |
| Status | Planned |
| Start | Sun 20 Dec 2026 |
| Due | Mon 21 Dec 2026 |
| Responsible | Akram — UI/UX designer |
| Co-responsible | — |
| Effort | 2 person-day(s) planned · 4 from scratch · size M |
| Area · app | Quality · shared |
| Depends on | DQA-04, MOB-12, DQA-05 |
| Unblocks | QA-01 |
| Milestones | — |
Summary
Akram executes the scripted functional scenarios (per SRS acceptance criteria) on staging builds and files defects.
Description
Akram runs the scripted functional test campaign on the staging builds of the four apps, after the design QA of the back-office and reseller web (DQA-04, DQA-05) and the mobile staging integration (MOB-12). Defects are filed with evidence. The scripts come from the SRS acceptance criteria and the 15 priority scenarios of cahier §12: Compte revendeur, Catalogue, Commande, Stock, Suivi, Promotion, Fidélité, Tournée, GPS, Prospect, Invitation, Première commande, Rapport, Permissions, Hors ligne. Fidélité is V2 and is recorded as not applicable to V1. The 17 Oct decisions are added: guest mode, three customer-type prices, availability-only stock, advanced filters, regional WhatsApp, after-sales and returns, manual confirmation and live order status. The campaign report feeds QA-01 (end-to-end integration testing with Anis and Imad), which depends on this task, and then the client acceptance QA-02 (OPS-05).
Subtasks
| # | Subtask | Owner |
|---|---|---|
| 1 | Write one script per scenario (preconditions, steps, expected result per step, requirement ids, apps involved) from /docs/srs/acceptance-scenarios and the requirements | Akram |
| 2 | Seed the staging test data: one reseller per customer type, a pending account, two delegates with zones and a planned tour, products with attributes in two categories, an active promotion, support regions with numbers | Anis |
| 3 | Account and catalog: sign-up with OTP and customer type → appears in BO-13 → approve; guest sees no price; each reseller type sees only its price; availability only; combined filters with counts | Akram |
| 4 | Orders and stock: checkout gives a CMD- number and lands Envoyée in BO-41; confirm → reservation; ship → deduction; cancel → release; return reception → automatic restock and credit note; promotion respects dates, target and stock cap | Akram |
| 5 | Tracking and support: back-office status changes appear live in RA and RW (SSE) and as push and inbox notifications; WhatsApp region resolution (signed in, guest with location, no location); after-sales claim → resolution | Akram |
| 6 | Field: start a tour, check-in inside and outside the 150 m tolerance, visit with photos, report creating a follow-up, prospect created without duplicate, invitation QR attributing the install to the right delegate, first order linked to reseller and source delegate, closing with a complete summary | Akram |
| 7 | Offline: visits, report and new reseller in airplane mode, then sync after the network returns with no duplicates; conflict surfaced in the sync centre | Akram |
| 8 | Permissions: for each role, unauthorised menu items are absent and direct URL or API access is refused (403); delegate and reseller data scope | Akram |
| 9 | File defects in the right repo with steps, expected vs actual, build version, device, screenshot or video and requestId; severity blocker / major / minor | Akram |
| 10 | Daily triage of the defects and fixes on staging | Imad |
| 11 | Re-test fixed defects and publish the campaign report (pass / fail per scenario, open defects, V2 not-applicable items) | Akram |
Deliverables
- Test scripts for the 15 cahier scenarios plus the 17 Oct decision scenarios
- Defects filed in
AnisBetehi/hocoandhoco-mobilewith evidence and severity - Campaign report: result per scenario, open defects, re-test status, handed to QA-01
Acceptance criteria
- Every V1 priority scenario has been executed on staging with real devices at least once and re-tested after fixes
- Each defect has reproducible steps, the build version and evidence
- No blocker defect remains open at the end of the campaign without an owner and a fix date
- The Fidélité scenario is explicitly marked V2 / not applicable
- The report is accepted by Anis as the input of QA-01
Requirements covered
| Requirement | Title | Release |
|---|---|---|
| OPS-05 | Acceptance: priority scenarios pass, blocking defects fixed, acceptance report (PV) signed | V1 |
Test measures
- Scenario pass rate tracked per day; blockers re-tested within one day of a fix
- Spot re-run of 3 passed scenarios on the final staging build to catch regressions
Risks
- Staging data or builds are unstable — agree a daily build cut-off with Anis and Imad and freeze the test data set; reset it from a seed script.
- One person cannot cover four apps in two days — prioritise the scenarios that the client recette (QA-02) will run first, and pair with Imad on the field scenarios.
KPI
- Delivered by Mon 21 Dec 2026 within 2 person-day(s).
- Every acceptance criterion above demonstrated before hand-off; linked requirements' acceptance criteria pass.
- Zero open critical defects, permission gaps or data-integrity regressions at sign-off.
Generated from content/plan/tasks.json by scripts/generate-team-tasks.mjs. Dates are computed by the scheduler (Sunday–Thursday weeks, holidays excluded) — change the plan, not this page.