Task library CHECK Quality engineering · Phased project Checkout regressions the team can reproduce A small commerce team has happy-path browser tests but still ships rounding and retry defects. Model a fictional shop using synthetic products, a local payment double, and explicit cart rules before adding regression coverage.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 20h 45m + setup
Suggested stack TypeScript · Playwright · HTTP · SQL Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with CHECK-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice risk-based test selection, stable browser automation, and diagnosis of intermittent failures.
What the team gains Review whether a test suite catches business regressions and explains failures without creating noisy release gates.
Before you start Create or provide a local checkout fixture application. Model products, tax rules, inventory, and a payment-provider double using synthetic data. Delivery agreement A local checkout fixture, regression suite, failure artifacts, and release-gate policy.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Establish realistic fixtures and observable expected behavior.
PHASE 2 Cover money, duplication, inventory, and access boundaries.
PHASE 3 Keep runs isolated, diagnosable, and honest about coverage.
Define the checkout contract Establish realistic fixtures and observable expected behavior.
CHECK-101 Entry ticket; project setup still required CHECK-102 Depends on CHECK-101 Exercise costly failure paths Cover money, duplication, inventory, and access boundaries.
CHECK-103 Depends on CHECK-101 CHECK-104 Depends on CHECK-102 Estimated field mix
Quality engineering 60% Distributed systems 40% CHECK-105 Depends on CHECK-101 Estimated field mix
Quality engineering 60% Database engineering 40% CHECK-106 Depends on CHECK-102 Estimated field mix
Quality engineering 60% Security 40% Turn checks into a useful release gate Keep runs isolated, diagnosable, and honest about coverage.
CHECK-107 Depends on CHECK-102 Estimated field mix
Quality engineering 50% Accessibility 50% CHECK-108 Depends on CHECK-104, CHECK-105, CHECK-106 Estimated field mix
Quality engineering 80% Database engineering 20% CHECK-109 Depends on CHECK-108 Estimated field mix
Quality engineering 60% Privacy engineering 20% Security 20% CHECK-110 Depends on CHECK-103, CHECK-107, CHECK-109 Estimated field mix
Quality engineering 80% Platform engineering 20% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.