Software Testing Fundamentals

Test harness and unit test framework tools primarily support test execution and logging. These tools automate running test cases, capture results, log execution details, and report pass/fail status. While some frameworks may have features for management (A), specification (B), or performance monitoring (C), their core function is executing tests and recording outcomes.

Usability testing evaluates how user-friendly an application's interface is. It focuses on the user experience, ease of navigation, intuitiveness of design, and overall satisfaction when interacting with the system. This is distinct from Regression testing (A) which checks for unintended changes, Performance testing (C) which measures speed and scalability, and Functional testing (D) which verifies specified behaviors.

Use Case testing identifies test cases that exercise the entire system from start to finish on a transaction-by-transaction basis. Use cases represent real-world user scenarios and workflows, making them ideal for validating end-to-end system functionality. Unit testing (B) focuses on individual components, State transition testing (C) examines system state changes, and Decision table testing (D) maps complex business rules.

To answer this question, the user needs to understand the different types of review.

A. Walkthrough: This is a type of review where the author of a document walks through it with other team members, stakeholders, or subject matter experts to ensure that everyone understands the content, and to identify any defects or issues that need to be addressed. This option is a type of review.

B. Inspection: This is a type of review that focuses on finding defects or issues in a document, code, or design. It is usually performed by a team of inspectors who are trained to find defects. This option is a type of review.

C. Informal Review: This is a type of review that is not structured and is usually performed by colleagues or peers. It is done to obtain feedback, identify potential defects, and gain a better understanding of the document. This option is a type of review.

D. Management Approval: This is not a type of review. It is a process that involves obtaining approval from management for a document, design, or code before it is released.

The Answer is: D

Review techniques like walkthroughs and inspections can be applied to any documented work product in software development. This includes software code, Requirement Specification documents, Test Design specifications, and other artifacts. Reviews are a static testing method that examines documents without executing the code.

Functional testing is classified as a test type (testing what the system does) rather than a test level. Component testing, System testing, and Acceptance testing are test levels (organizational levels of testing). The ISTQB classification of test types includes functional testing, non-functional testing (performance, usability, etc.), and white-box/structural testing as the main categories.

Structure-based testing techniques (also called white-box testing) analyze the internal structure of the code. Their key characteristic is that they are used both to measure coverage (like statement coverage, branch coverage) and to design additional tests specifically to increase that coverage. This distinguishes them from experience-based techniques and specification-based techniques.

A test level is a group of test activities organized and managed together. The standard test levels are component testing, integration testing, system testing, and acceptance testing. Each level has specific objectives, like unit testing for individual components, integration testing for interfaces, system testing for the whole system, and acceptance testing for user requirements.

A test manager is defined as the leader of a test team or teams, responsible for planning, monitoring, and controlling test activities. This role is distinct from a test leader (who might manage a specific project or subset of tests), and involves managing people, resources, and the overall test strategy rather than just executing tests.

BVA stands for Boundary Value Analysis, a black-box test design technique that focuses on testing at the boundaries between equivalent partitions. For example, if a field accepts 1-100, boundary tests would check 0, 1, 2, 99, 100, and 101. Defects often occur at boundaries because developers may use incorrect comparison operators.

Static analysis tools examine code without executing it, looking for defects like coding standard violations, security vulnerabilities, unreachable code, and potential bugs. These tools are most useful to developers during coding and unit testing, as they provide immediate feedback on code quality and can prevent defects before dynamic testing begins.

Debugging is the process of investigating, locating, and repairing the cause of a software defect after it has been identified (usually through testing). It includes activities like reproducing the defect, analyzing the root cause, implementing a fix, and verifying the correction. Debugging is a development activity, NOT part of the fundamental testing process (which includes planning, specification, execution, and completion).

Exploratory testing is an approach where test design, test execution, and learning happen simultaneously. The tester actively explores the system, learns about its behavior, and designs and executes tests based on what they discover. It's concurrent and interactive, unlike scripted testing where tests are designed before execution. Key elements are concurrent test design, execution, logging, and continuous learning about the system.

Under standard testing definitions (such as ISTQB), a test condition is defined as any item, element, or event of a component or system that can be verified by one or more test cases; hence, 'something that can be tested'. An input and expected outcome define a test case instead.

Test data preparation tools help generate, manage, and manipulate test data needed for testing. These tools support the test specification and design phase by allowing testers to create subsets of production data, generate synthetic data, or anonymize sensitive data. This ensures that appropriate test data is available when designing test cases, rather than during execution or management phases.

Control flow refers to the sequence of events or execution path through a component or system. It describes the order in which statements or instructions are executed, including branches, loops, and decision points. Control flow analysis is important for white-box testing, coverage measurement, and understanding how different inputs affect the execution path through the code.

In software testing, 'bug' is synonymous with 'defect' - a flaw in the code that causes incorrect behavior. 'Error' and 'mistake' refer to human actions that lead to bugs being introduced, while 'incident' refers to the result of executing a bug. Option B, 'Defect,' is the formal testing term that directly corresponds to 'bug.'

Black box testing focuses on inputs and outputs without knowledge of the internal code structure. It's also called 'specification-based' or 'behavioral' testing because tests are designed based on requirements and specifications rather than code implementation. White box is 'structural-based,' testing internal logic.