Static Testing Techniques Overview
Uploaded by
Fahama Bin EkramStatic Testing Techniques Overview
Uploaded by
Fahama Bin EkramCommon questions
Powered by AIStatic testing improves software development efficiency by identifying and removing defects early in the development process. By reviewing requirement specifications, system designs, and code without executing it, errors can be detected early, reducing the likelihood of complex defects later in the development cycle. This practice, particularly reviews, enhances clarity and reduces ambiguity, allowing developers to write code more quickly and with fewer errors . Additionally, by reducing defects before the code becomes executable, fewer errors need to be addressed during dynamic testing, thereby decreasing testing costs and time delays .
Code walkthroughs and formal inspections differ primarily in their level of formality and their structured approach. Walkthroughs are less formal and usually involve a group reviewing the code where multiple perspectives are considered, but only questions raised by the team are addressed, limiting completeness to those areas . Formal inspections, however, are highly structured and aim to detect all faults through thorough preparation, role assignments, and a methodical review process. Inspections demand more rigorous preparation and involve specific roles such as a moderator, inspectors, and a scribe to ensure comprehensive defect identification .
Reviewing specification documents early is crucial for defect prevention because it helps identify and correct ambiguities and errors before they propagate into later development stages as code. This early intervention decreases the chance of defects becoming embedded in executable code, which would be more costly and time-consuming to address. It also ensures that work products are clearer and unambiguous, streamlining subsequent development phases .
Completeness varies between desk checking and code walkthroughs. Desk checking is an informal process where programmers verify their code corrections against design specifications without any structured methods, potentially leading to overlooked errors due to lack of completeness and recording . In contrast, code walkthroughs, though still less formal than inspections, involve a group who look at the code together, ensuring more comprehensive coverage through varied perspectives, but completeness is limited to the questions raised during the session .
Formal inspections differ from other review methods in their rigorous focus on thoroughly detecting all possible faults, violations, and side effects in the code. They employ a structured method involving specific role assignments (author, moderator, inspectors, scribe) ensuring a comprehensive evaluation. In contrast, other review methods like desk checking and code walkthroughs have less structured approaches, making them more suitable for identifying straightforward or surface-level issues rather than systematically detecting all potential problems .
Reviews reduce delays in test execution phases by eliminating defects before code execution begins. This proactive defect detection prevents the need for delayed test corrections after failures occur, thus avoiding the time testers would spend waiting for fixes and retests. By ensuring a cleaner codebase, test execution can proceed more efficiently, with fewer interruptions due to defect remediation .
Reviews enhance communication among developers by facilitating discussions and collaborations on documents where ambiguity and errors may exist. This process helps clarify the authors’ intents and ensures all team members understand what is being developed. Through the review process, authors and peers refine ambiguous content, leading to improved documentation and aligning the team's understanding and expectations, thereby reducing potential misunderstandings later in the cycle .
The review process contributes to cost reduction by allowing defects to be detected and corrected early in the software development life cycle. This reduces the need for additional resources and time that would otherwise be required to address defects in executable code. Early detection through reviews mitigates delays in the test execution phase and ensures fewer failures, leading to decreased lifetime support costs for the final software product. Communicative clarity and refined documentation further reduce misunderstandings and associated costs .
Review processes typically identify defects such as deviations from standards, ambiguous or missing requirements, design flaws not aligning with requirements, insufficient maintainability due to complex code, and incorrect interface specifications. Different types of reviews, such as desk checking, code walkthroughs, and formal inspections, focus on finding these defects effectively and efficiently .
Conducting a formal inspection only when the code is ready is important because it ensures that the inspection process is as effective as possible. If the code is not in a reasonable state of readiness, with basic desk checking and walkthroughs already performed, formal inspections may miss certain defects or waste time reviewing incomplete sections. A prepared codebase allows inspectors to focus on identifying deeper structural issues, violations, and side effects rather than basic errors that should have been remedied earlier .