STEP 3: Prioritize code areas
Typically, this step is done by QA Manager and the related Engineering Manager / Dev Team Lead / Tech Architect.
Facing a mountain of untested code changes with limited resources? Don't panic! Tackle it smartly with prioritization.
The key: break down your codebase into manageable subsets. Focus on one chunk at a time, addressing critical areas first. This "divide and conquer" approach delivers several benefits:
Faster results: See quicker progress towards your quality goals.
Sharper focus: Channel your limited resources effectively.
Increased confidence: Gain greater trust in your software's overall quality, one step at a time.
There are several effective ways to prioritize code areas:
Add Code Labels: Apply code labels to mark critical areas of your codebase, helping you create a subset of code that requires immediate attention.
Ignore Irrelevant Code: Exclude parts of your code that are not pertinent to the testing process. By focusing solely on the relevant sections, you can streamline your testing efforts.
Perform a Deep CSV Analysis: Conduct a detailed analysis using a CSV file to gain more in-depth insights into the test gaps and identify high-priority areas.
We highly recommend starting with the implementation of code labels as the first step to create a subset of your code.
Last updated