Effective QA Participation in Technical Design Review: Guidelines and Best Practices

Background : QA at ZuanZuan strives to shift testing left, joining projects early to catch and resolve issues, with technical design review being a core activity to prevent costly rework.

Goal : Enable QA to effectively participate in technical design reviews, avoid requirement misunderstandings, help R&D refine designs, and prepare for subsequent testing phases.

Typical QA states during design reviews :

Listening without commenting – no preparation or familiarity with the design.

Unable to understand but can ask questions – needs explanations.

Understands and can spot issues – provides valuable suggestions.

1. Technical Design Requirements : A standard outline (business flow, core design ideas, interaction details, change & regression impact, test suggestions, sandbox & production plan, review minutes) that all parties should address.

2. Pre‑Review Preparation :

2.1 Requirement analysis conversion – map business scenarios and core functions.

2.2 Familiarize with technical documents – read the design thoroughly.

Reading Goals :

Understand the design.

Compare with own ideas to find the better solution.

Audit for missing scenarios and potential problems.

3. Technical Design Review :

3.1 Thinking methods – forward, reverse, combination, simple, global, user‑centric, comparative, process‑oriented.

3.2 Core focus – enumerate exception cases, avoid duplicate business logic, consider performance (resource‑intensive ops, caching, pagination), ensure data consistency (transactions), handle version compatibility.

3.3 Impact assessment – evaluate code changes and alternative designs on functionality and test scope.

3.4 Improve testability – add key logs, provide back‑doors, prepare test data constructors, clarify hard‑to‑test areas.

Case Example : Designing an online auction marketplace (create auction halls, publish items, handle caching, idempotency, and data consistency). The example illustrates how to apply the above checklist to real business scenarios.

Results :

Refined technical designs by uncovering requirement gaps.

Guided test‑case selection and mock construction for higher efficiency.

Enhanced white‑box testing mindset and faster bug localization.

Improved project planning by accurately estimating complexity and regression scope.

Final Note : Delivering high‑quality products requires collective responsibility; QA should question designs early, leverage business knowledge, and continuously build a mindset that prevents bugs at the source.