Software Testing and Quality Control

Defect Clustering and Pesticide Paradox are both established principles of testing. Defect Clustering states that a small number of modules contain most defects, while Pesticide Paradox observes that repeating the same tests eventually becomes ineffective as they stop finding new defects. Since both are valid principles, option C (Both 1 & 2) is incorrect, making D (None) the correct answer.

WinRunner, QTP (QuickTest Professional), and RFT (Rational Functional Tester) are all functional testing tools used for automated testing of applications. QC (Quality Center), now known as ALM (Application Lifecycle Management), is a test management tool used for managing the testing process, not for executing functional tests. This makes QC the correct answer as the non-functional tool.

Object Spy is a QTP diagnostic tool that allows viewing the supported properties, methods, and operations of any object in an open application. It's used for inspection and understanding object structure, not for defining actions, naming objects, or deleting from repository.

Reusable actions can be invoked multiple times within a test and from other tests, promoting modularity. They cannot be merely copied as independent actions nor are they uncallable; thus the other statements are false.

In software testing terminology, a 'Failure' is the deviation from specified or expected behavior that is visible to end-users. An error or mistake refers to the human action that caused the issue, a fault or defect is the imperfection in the code, but the observable incorrect behavior is called a failure.

A failure is the observable incorrect behavior that users see. A fault is the defect in the code that causes failures. An error is a human mistake that may introduce faults. A defect is similar to a fault, a flaw in the code. The distinction: error leads to fault leads to failure.

Beta testing involves customers using the software in their own environment with real data, unlike alpha testing which is conducted at the developer's site by internal staff. Independent test teams perform testing at various stages, and early lifecycle testing is a strategy not specific to beta testing.

A test incident report documents the problem: what happened, not how to solve it. Essential elements include reproduction steps (B), test environment details (C), severity/priority (D), and actual vs expected results (E). The solution (how to fix) is a developer task determined during debugging, not part of the incident report.

Static testing examines artifacts without running the software: walkthroughs, inspections, and data flow analysis are examples. Error guessing involves designing and executing test cases based on intuition about where defects might exist, making it a dynamic testing technique that requires running the software.

When users find faults, it indicates both quality issues in the software (faults exist) and gaps in the testing process (they weren't caught before release). Insufficient time (D) can contribute to poor testing, but poor quality software (A) alone doesn't explain why users found them: testing should have caught them. Bad luck (C) is not a systematic cause.

Finding faults during planning is most cost‑effective because defects detected early require minimal rework. Later activities like design, execution, or exit‑criteria checks are progressively more expensive, and the other choices do not offer the lowest remediation cost.

Verification checks that the product is built correctly according to specifications—"building the system right". It is not about building the right system (validation), nor is it defined by who performs it, making the other options inaccurate.

Cyclomatic Complexity measures the number of independent paths through code by counting decision points (predicates). It's calculated from the control flow graph, requiring knowledge of the code structure, making it a white-box testing technique. Black-box testing (B) doesn't examine code structure. Green and yellow box are not standard testing categories.

Error guessing is applied after formal techniques such as boundary value analysis or equivalence partitioning have been used, because it relies on tester intuition to uncover hidden defects. It is not the first approach, nor is it limited to inexperienced testers, post‑production use, or end‑user activities, which makes those options incorrect.

A test strategy provides a structured approach to testing that ensures comprehensive coverage and risk mitigation. Option D is most correct because it emphasizes the critical business impact and potential consequences of software failure - including financial loss, reputational damage, and safety risks. While options A, B, and C describe valid benefits of test planning, option D addresses the fundamental reason testing exists: to prevent serious negative outcomes. A proper test strategy aligns testing effort with business risk and provides stakeholder confidence in system reliability.