Software Testing Fundamentals: Reviews, Static Testing, and QC

In a walkthrough, the author leads the presentation of their work to colleagues, making it an informal review process. In an inspection, a trained moderator (who is not the author) leads a formal review following specific procedures and documentation requirements. Option D correctly states this key distinction.

Requirements traceability helps track which requirements are tested, identify impacted requirements when changes occur, and verify test coverage. However, it does not track test execution statistics. Option C is correctly identified as NOT a benefit of traceability.

The IEEE 829 standard defines a Test Plan template containing sections like test items, deliverables, and tasks. A test specification is a separate document type altogether under the standard rather than a component or section of the test plan document itself.

Early test design prevents fault multiplication (statement i), finds faults early (statement iii), and can trigger requirement changes when issues are discovered (statement iv). Faults found early are actually LESS expensive to fix (statement ii is false), and while it requires effort, saying it 'takes more effort' is misleading compared to the cost of late fixes (statement v is false).

Software engineers typically evaluate and rank tools but do not make final purchasing decisions. Their role is to identify options, assess technical fit, and make recommendations to management who authorize the actual purchase. Option A correctly describes this advisory role.

Static testing involves examining software artifacts without running the code. This includes manual examination of documents and code, automated analysis tools, and reviewing project documentation. Option A (execution of software) is the only activity that does NOT belong to static testing.

Static testing finds defects in documentation or code without executing the software. These defects, if left in the software, would eventually cause failures when the code runs. Option B correctly identifies that static testing finds the causes of potential failures.

All options A, B, and C describe real benefits of reviews. When a question asks what benefits are included and lists 'all of the above,' the correct answer is D. Reviews do provide early defect detection, productivity improvements, fewer defects, and better communication.

In a formal review process, the sequence is Planning -> Kick-off -> Preparation -> Review meeting -> Rework -> Follow-up. Rework immediately follows the review meeting, where the author addresses issues identified. Option D correctly identifies Rework as the next activity.

In a formal review meeting, the scribe (also called recorder) is responsible for documenting all issues, problems, decisions, and open points identified during the discussion. Option C correctly identifies this role.

Static analysis is examination of code without execution, which is performed using automated tools that check for coding standard violations, security issues, and potential defects. The statement is correct.

An inspection is a formal review process led by a trained moderator who is not the author. The moderator ensures the inspection follows defined procedures and manages the review team. Option C correctly identifies the moderator as the leader.

Walkthroughs, technical reviews, and inspections are all formal peer review methods designed to find defects through collaborative examination. These activities can be conducted within a peer group where colleagues review each other's work, making the statement true.

HP Quality Center (QC) was originally developed by Mercury Interactive and called 'Test Director' before being rebranded. The tool provided foundational testing management capabilities and evolved through multiple name changes (Quality Center, ALM) while maintaining its core testing workflow functionality. This historical naming reflects the product's evolution from a test-focused tool to a broader quality management platform.

Quality Center (now Application Lifecycle Management) is enterprise software designed to run on multiple operating systems. It supports Windows servers as the primary deployment platform, Linux-based systems for enterprise environments, and Unix variants like Solaris for legacy or specialized enterprise deployments. The web-based client further extends accessibility across platforms.

Quality Center provides comprehensive testing process management including requirement definition and tracking, test execution management, and defect tracking workflows. The 'Requirements' module captures release needs and specifications, 'Test Lab' executes tests, and 'Defects' module tracks bugs. These integrated functions make QC a complete testing lifecycle solution.

In Quality Center's hierarchical structure, a Release represents a major deliverable containing multiple features or requirements. Each release is divided into Cycles, which are time-bound iterations or testing phases. This hierarchy allows teams to organize testing work by release milestones and then break them into manageable cycles. This is the standard organizational model in QC/ALM.

The Test Plan Tree in Quality Center hierarchically organizes all tests into folders and subfolders based on application structure, functional areas, or testing units. This tree structure allows teams to group related tests together (by subject area or feature) and maintain an organized, scalable test repository. The Test Lab focuses on execution sets rather than hierarchical organization.