testing Online Quiz - 71

The V-model is a software development model that links each development phase with a corresponding testing phase. Its key principle is that modules are validated against user requirements through verification and validation activities. Option B correctly captures this fundamental testing principle.

Testing stops when predetermined completion criteria are met, not when arbitrary fault counts are reached or specific test categories finish. Good test planning defines exit criteria based on risk, coverage, and quality thresholds. Statement coverage alone is insufficient as a stopping criterion.

A test plan typically includes features to be tested, risks, schedule, and scope. Incident reports are outputs of test execution, not inputs to planning. They belong in test summary reports, not the plan itself. The plan documents what will be tested and how, not results from testing.

To answer this question, the user needs to know about white box testing techniques.

White box testing techniques are also known as structural testing techniques. These techniques are used to test the internal structure of the software system. In white box testing, the tester has knowledge of the internal workings of the system being tested.

Now, let's go through each option to determine which one is NOT a white box technique:

A. Statement testing: This is a white box testing technique where each statement in the source code is executed at least once. The purpose of this testing is to ensure that every statement in the code has been executed and tested.

B. Path testing: This is a white box testing technique where all possible paths through the software are tested. The purpose of this testing is to ensure that all logical paths through the software have been executed and tested.

C. Data flow testing: This is a white box testing technique where the flow of data through the software is tested. The purpose of this testing is to ensure that data is correctly input, processed, and output by the software.

D. State transition testing: This is a black box testing technique that tests the response of the system to different input conditions. The purpose of this testing is to ensure that the system responds correctly to different input conditions.

Therefore, option D is NOT a white box technique. It is a black box technique.

The Answer is: D

When prioritizing testing, the most important objective is to test high-risk areas first. This maximizes value by focusing on where failures would cause the most damage. Finding many faults in low-risk areas is less valuable than finding critical faults in high-risk functionality.

Testing object-oriented class operations is complicated by inheritance and polymorphism. Inheritance creates complex relationships where a test for a parent class may need to cover child classes. Polymorphism means the same operation can behave differently depending on object type, requiring more comprehensive test coverage.

Cyclomatic complexity is a software metric that measures the number of independent linear paths through a program's source code. It quantifies decision logic complexity by counting branching points. This metric helps identify areas needing thorough testing, as higher complexity indicates more paths to verify.

White-box testing (also called glass-box or structural testing) examines the internal structure, code, and logic of a software module. Unlike black-box testing which focuses on inputs and outputs, white-box testing requires knowledge of the internal implementation to design test cases that cover paths, branches, and statements. Behavioral testing is a broader concept unrelated to internal logic examination.

The IFPUG (International Function Point Users Group) Functional Size Measurement Method uses Function Points (FP) as its unit of measure. Function Points quantify the functionality provided to the user based on the application's inputs, outputs, inquiries, external interfaces, and internal files. External Interface Files (EIF) and Internal Logical Files (ILF) are components counted within the Function Point analysis, not the unit itself. Feature Points is a different sizing method.

There is no fixed percentage allocation for development and testing budgets because project requirements vary. The budget split depends directly on the criticality of the application, regulatory requirements, and risk factors, making standard splits like 50-50, 40-60, or 60-40 inaccurate generalizations.

A Business Analyst (BA) is responsible for capturing business requirements in the BRD and mapping them to test cases using the Requirements Traceability Matrix (RTM). The Design/Development Lead (DL) designs the solution, the Project Sponsor authorizes and funds the project, and VTM is not a project role.

The Business Analyst (BA) is responsible for producing design specifications in a project. BAs bridge business requirements and technical implementation, documenting system behavior, user interactions, data structures, and business rules. VTM (likely Team Lead), DL (possibly Delivery Lead), and SPONSOR are roles focused on delivery management, governance, and funding rather than detailed specification creation.

Requirement defects are raised after FPQ (likely Final Product Qualification or Formal Product Qualification). Before FPQ, requirements are still being clarified and finalized; raising defects during this stage would be premature as the requirements themselves may change. After FPQ, requirements are baselined, and any deviations from agreed requirements become legitimate defects. HLE (likely Higher Level Examination or High-Level Engineering) typically occurs earlier in the lifecycle.

Boundary Value Analysis (BVA) is the technique described. BVA complements Equivalence Partitioning by focusing test cases at the edges of equivalence partitions (minimum, minimum-1, maximum, maximum+1), where defects are most likely due to off-by-one errors. Equivalence Partitioning divides inputs into classes but doesn't specifically target edges. State transition and cause-effect graphs address different testing concerns.

The DELPHI estimation technique uses a forecasting approach based on expert consensus through iterative anonymous rounds. Experts provide estimates, discuss aggregated results, and refine their forecasts until convergence. FPA (Function Point Analysis) is a sizing method, SWAG is a rough guess, and Production Standards are based on historical data rather than forecasting. Delphi explicitly uses forecasting methodology.

ClearCase supports creating personal views with customized settings, similar to QC's (Quality Center) personalization features. A ClearCase view defines a specific configuration of elements (versions, branches, directories) tailored to the user's needs. This statement is true - both tools allow users to create personalized working views. False would incorrectly imply ClearCase lacks this capability.

ClearCase does allow writing to elements that are in check-out mode. The checkout operation specifically locks the element for modification by the user, creating a writable copy in their view. This is fundamental to version control - you check out to edit. The answer Yes is correct. No would imply checkout is read-only, which contradicts the purpose of checkout.

ClearCase does not support the MS DOS operating system. ClearCase requires modern operating systems like Unix/Linux, Windows NT-based systems, or macOS. MS DOS is a legacy 16-bit OS that lacks the filesystem, security, and multitasking features ClearCase requires for its version control operations. The answer No (option B) is correct.