Software Testing and Quality Control

A static defect is one raised for document correction, such as requirements, design specs, or test plans. Unlike dynamic defects found during execution, static defects are identified through reviews and inspections without running code.

In software testing, a defect is logged when the actual observed behavior of the system does not match the expected behavior defined in the test cases or requirements.

Bugzilla is a defect tracking tool used to manage and track bugs and issues in software development projects. It's not for detection, test case management, or XML generation.

Mercury Quality Center (now HP Application Lifecycle Management/ALM) is a comprehensive test management tool that tracks test execution progress, manages test cases in the Test Plan module, and maintains requirements in the Requirements module.

In Mercury Quality Center, test cases are written in the Test Plan tab. Requirements are in the Requirements tab, Test Lab is for execution, and there is no separate Test Case tab - test cases live within Test Plan.

A test case is marked BLOCKED when it cannot be executed because a dependency (another test case, prerequisite, or feature) is failing or not available. It's not about time constraints, scope, or external requests - it's about technical dependencies blocking execution.

When a developer rejects a defect, the tester should review the developer's justification. If the tester disagrees with the rejection (believes the issue is valid), they should reopen the bug. Never close without verification or reopen automatically - always evaluate the rationale first.

E2E tests validate complete workflows from start to finish, including all intermediate systems and third-party integrations. Option D correctly captures the round-trip nature where a test originates from the gateway, traverses third-party systems, and returns to the gateway.

In BBE testing, business errors specifically refer to errors that originate from third-party systems or services, distinguishing them from internal technical failures. Option C correctly identifies this classification.

Severity in defect management measures the potential damage a defect can cause to system functionality, data integrity, or user experience. It is unrelated to frequency or resolution time - those are priority metrics.

Static defects are documentation or specification errors identified during review, not during actual test execution. They exist in requirements, design documents, or test plans rather than in running code.

A defect is logged whenever actual test results diverge from expected results, regardless of whether it's a technical, business, or data error. This mismatch indicates a genuine issue requiring investigation.

ISO/IEC 14143 'Information technology - Software measurement - Functional size measurement' is the international standard for software measurement, specifically focusing on function point analysis (FPA). It provides the framework for measuring software functional size. 12119 covers software package quality requirements, 15504 covers process assessment, 15271 relates to IT service management, 12207 defines life cycle processes, and 15939 covers the measurement process (not measurement itself).

Exit criteria define the specific conditions, coverage targets, and quality thresholds that must be met to determine when a test level or testing phase has been completed.

Test reporting should focus on both technical details (boundary conditions, state machines, load generators) AND business impact (risk management, reputation, revenue impact from test escapes). Option C correctly combines both aspects.