Software Quality Assurance Practice Exam

Select the descriptions that match Desk Checking

1. Runs counter to testing principle two, which states that people are generally ineffective in testing their own programs

2. Follows undisciplined process of testing and finding errors

3. Evaluates anonymous programs for their overall quality, maintainability, and so on

4. Allows for user feedback during testing

The correct answer is: Runs counter to testing principle two, which states that people are generally ineffective in testing their own programs

Desk checking is a manual review process where the programmer examines the code or documentation for errors before it is executed. It entails reviewing the code line by line and simulating its execution mentally or on paper. This process primarily relies on the programmer's understanding and can be limited by their ability to see flaws in their own work. The first choice correctly identifies a challenge associated with desk checking. It highlights that individuals may struggle to identify errors in their own code due to bias or familiarity, which can diminish the effectiveness of this method. This principle aligns with the understanding that independent testing is often more reliable, as individuals not intimately involved with the code may catch issues that the original developer overlooks. In contrast, the other choices do not accurately reflect the nature of desk checking. The mention of a "follow undisciplined process" suggests a lack of structure, which is not true for desk checking as it is a methodical review of code. Evaluating "anonymous programs" contradicts the fact that desk checking typically examines code created by the individual conducting the review. Finally, user feedback would generally occur during more formal testing phases, rather than during the desk checking process, which is an individual activity focusing on the programmer's own code.