Software Testing Fundamentals

Functional testing evaluates software based on functional requirements - what the system should do from a user perspective. It verifies that each feature of the software operates as specified in the requirements document, making 'Functional testing' the correct answer.

Boundary Value Analysis is a black box testing technique that focuses on testing values at the boundaries (edges) of input ranges, such as minimum and maximum values. Many defects occur at boundaries, making them critical test points. Equivalence partitioning divides inputs into classes, error guessing uses intuition, and state transition testing analyzes system states.

Ad-hoc testing is informal, unstructured testing without formal test documentation or plans. It is inherently manual as it relies on tester intuition, exploration, and creativity to find defects. While automation can support testing, ad-hoc testing by definition is an exploratory manual approach.

A Requirements Traceability Matrix (RTM) maps each requirement to one or more test cases, creating a bidirectional trace that ensures every requirement is tested and allowing verification that no requirement has been missed.

The question describes executing the same test case with different input values, which is commonly used to verify functionality across various scenarios. Re-testing refers to running tests again after fixes, while regression testing checks that changes haven't broken existing functionality.

Usability testing evaluates how easy and intuitive a user interface is for end users. It's a non-functional testing type that assesses user experience, learnability, and efficiency rather than specific functional requirements.

White box testing requires knowledge of internal code structure. Glass box, open box, and clear box all refer to seeing inside the code. 'Closed box' refers to black box testing where internal implementation is hidden.

Boundary value analysis tests at the edges of input ranges (minimum, maximum, just inside/outside boundaries). This technique focuses on inputs and outputs without examining internal code, making it a black box testing method.

Static techniques analyze code without executing it (Data Flow Analysis and Inspections), while dynamic techniques require running the system with test inputs. Equivalence Partitioning, Use Case Testing, Exploratory Testing, and Decision Testing all involve executing the system, making them dynamic. Static analysis happens before runtime, dynamic testing happens during runtime.

Static and dynamic testing both aim to improve quality by identifying defects, but they are complementary because static testing evaluates code without execution to find source errors, whereas dynamic testing executes code to identify runtime behaviors and functional failures.

Static analysis can detect coding issues like undefined variables, unreachable code, and array violations by examining source code structure. However, memory leaks are runtime behavioral issues that depend on execution patterns, resource allocation timing, and object lifecycle - these cannot be determined through static code examination alone. Memory leak detection requires runtime monitoring and profiling tools.

The tax brackets create boundaries at $4000 (tax-free limit), $5500 ($4000 + $1500 where 10% band ends), and $33500 ($4000 + $1500 + $28000 where 22% band ends). Option D has $4000 (first boundary), $4200 and $5600 which span the first two equivalence partitions ($0-$4000, $4001-$5500, $5501-$33500). These three values fall into different tax calculation scenarios, making them proper equivalence class representatives.

The specification creates three equivalence partitions: under 18 (no insurance), 18-30 inclusive (discount eligible), and over 30 (no discount). Values 18, 29, and 30 all fall within the same partition (18-30 inclusive) and would receive the same 20% discount. The other options mix values from different partitions (17 is under 18, 31 is over 30).

For a boundary range of 1900 to 2004, the traditional two-value boundary testing covers values just inside and outside the limits: 1899 (invalid low), 1900 (valid low), 2004 (valid high), and 2005 (invalid high). This makes option 628624 the correct choice.

Statement Coverage, Condition Coverage, and Path Coverage are all valid logic coverage techniques used in white-box testing. 'Pole Coverage' is not a standard term in software testing - it appears to be a made-up or misspelled term. The correct terms are Statement Coverage (each statement executed), Condition Coverage (each condition true/false evaluated), and Path Coverage (all possible paths taken).

Boundary Value Analysis tests values at the edges of equivalence partitions. The tax boundaries are at $4000, $5500 ($4000+$1500), and $33500 ($4000+$1500+$28000). For the upper boundary of the 22% bracket, $33500 is the last value taxed at 22%, and $33501 is the first value taxed at 40%. This makes $33501 a valid boundary test case for the transition to the highest tax rate. Option A ($28000) and C ($32001) are mid-range values, not boundaries. Option D ($1500) is not a tax boundary.

Statement Coverage only verifies that each statement has been executed at least once. It does not detect missing statements that should exist but were never written - this requires requirements or specification review. Unused branches, dead code, and unused statements are all present in the code and would be detected by statement coverage (or lack thereof). Missing code is fundamentally invisible to coverage tools.

Black box testing techniques test software without examining internal code. LCSAJ (Linear Code Sequence and Jump) requires analyzing code structure to identify linear sequences and jump points, making it a white-box technique. State transition testing, syntax testing, and boundary value analysis all focus on external behavior without needing to see the code.

Typical inspection costs cover setting up resources, reviewing material, meetings, and process improvement. Writing the document itself is a development cost, not a quality control or inspection cost. Therefore, it is correctly excluded from inspection overhead.

The question asks you to match review types to their characteristics. Walkthroughs are led by the author (v=1). Informal reviews are undocumented (u=2). Peer reviews have no management participation (t=3). Inspections are formal processes led by a moderator with defined entry and exit criteria (s=4,5). Option A correctly maps all these pairs.