sumo-qa-preparing-for-work

To create a QA plan before coding, identify 3–7 named risks anchored to specific file paths or domain terms, then map each risk to a minimal test set. This approach forces a senior-QA style brief instead of generic checklists by linking every test directly to a named risk.

The smallest useful test set is a collection of 3–7 concrete tests where each test directly targets one named risk. No test is written without a corresponding risk, ensuring coverage remains focused on the affected surface and observable outcomes.

You select one named testing technique per risk from an ISTQB-grounded catalogue. Specialty tooling is suggested only when it clearly fits the specific risk, keeping the QA plan focused on appropriate techniques like mutation testing, test selection, or risk analysis.

Yes, this QA planning approach applies to refactors, feature work, and ticket-driven changes. It requires reading scoped repository files to identify change-anchored risks tied to the affected surface, making it suitable for pre-coding risk analysis.

Test plans become generic checklists when risks are not anchored to specific file paths or domain terms. By identifying 3–7 named, change-anchored risks and mapping each to a minimal test set, you ensure every test probes a specific observable outcome.

Yes, risk analysis reduces unnecessary tests by mapping each identified risk to a minimal test set. By assigning one technique per risk from an ISTQB-grounded catalogue, you ensure the smallest useful test set without sacrificing coverage of the affected surface.