Test plans, risk-based testing, defects, shift-left
Practise these as flashcards. One or two lines each; the ones you miss come back first.
Start freeA test plan is a detailed document for a specific project or release, outlining what will be tested, how, by whom, and when. A test strategy is a high-level approach that guides testing across projects, describing overall objectives, methods, and standards.
Equivalence partitioning is a technique where input data is divided into groups that should be treated the same by the system. You then test one value from each group, which reduces the number of test cases needed while still covering all scenarios.
Severity describes how much the defect impacts the system or user, while priority indicates how soon it should be fixed. For example, a typo is low severity but may also be low priority, whereas a crash is high severity and usually high priority.
Exploratory testing is an unscripted approach where testers use their knowledge and intuition to find defects by actively exploring the application, rather than following predefined test cases.
I use risk-based testing to prioritize areas that have the highest business impact or likelihood of failure. This means focusing on critical features, areas with recent changes, or components with a history of defects before moving to lower-risk areas.
Boundary value analysis focuses on testing the edges of input ranges, as defects often occur at these boundaries. For example, if an input accepts 1-100, I would test 0, 1, 100, and 101 to ensure proper handling.
A defect is reported, triaged, assigned a severity and priority, then assigned to a developer for fixing. After the fix, QA verifies the resolution and closes the defect if it's resolved, or reopens it if not.
Shift-left testing moves testing earlier in the development process, often integrating it into CI pipelines. This helps catch defects sooner, reduces rework, and improves overall product quality and delivery speed.
I use decision tables to map combinations of input conditions to expected outcomes, which helps ensure all business rules and logic paths are tested, especially when there are multiple variables involved.
I focus on actionable metrics like defect leakage (bugs found after release), test coverage, and mean time to detect and fix defects. These help assess both the quality of testing and the product.
Test automation helps execute repetitive and regression tests efficiently, increases coverage, and provides faster feedback, especially when integrated with CI/CD pipelines. It allows manual testers to focus on exploratory and complex scenarios.
I use scripted tests for regression and core functionality, ensuring repeatability and coverage. I allocate time for exploratory testing to find unexpected issues and validate areas not covered by scripts, especially after major changes.