Software Testing and Quality Control

Code coverage measures how thoroughly tests exercise the codebase, making it a metric for Test Effectiveness. It doesn't directly measure defects found (that's defect density). Trend analysis is a separate use of coverage data. Time spent is an efficiency metric, not effectiveness.

Impact Analysis identifies which parts of the system are affected by a change, enabling teams to determine the scope of regression testing needed. Exit Criteria are defined by test planning. Number of test cases is a planning output, not an impact analysis decision. Tools selection is a separate consideration.

Impact Analysis identifies which parts of the system are affected by a change, enabling teams to determine the scope of regression testing needed. Exit Criteria are defined by test planning. Number of test cases is a planning output, not an impact analysis decision. Tools selection is a separate consideration.

Testing is fundamentally about finding defects (option D). Options A, B, and C describe 'showing that the program works' or 'is defect free' - these are impossible to prove and represent destructive thinking. The correct mindset is that testing can only prove defects exist, not that they don't.

Testing is fundamentally about finding defects (option D). Options A, B, and C describe 'showing that the program works' or 'is defect free' - these are impossible to prove and represent destructive thinking. The correct mindset is that testing can only prove defects exist, not that they don't.

In software testing terminology, a failure is the observable deviation from expected behavior that end-users experience. A fault or defect is the actual bug in the code, while an error refers to the human mistake that led to the fault being introduced.

BVT (Build Verification Testing) is a type of regression testing that verifies core functionality after a new build. It ensures the application is stable enough for further testing. It's not performance, volume, or security testing.

BVT is typically performed by developers as part of the build process, but testers can also run BVT suites. This is a standard practice in software development where smoke tests or sanity tests are executed after deployment.

BVT (Build Verification Testing) typically consists of Build Validation, which ensures the build is stable enough for testing, and Build Acceptance, which confirms the build meets the basic requirements to enter the test cycle. Other options use redundant or incorrect terminology.

HP Quality Center (now Micro Focus ALM) is a web-based test management tool used for managing testing processes, not test automation, test case design, or load testing. Option B is correct.

The Requirements module is the designated place in Quality Center where you create and link tests to requirements, ensuring each requirement has test coverage. This establishes traceability from requirements through test execution.

In Quality Center, traceability is bidirectional: Requirements show Test coverage (linked tests), and Test Plan shows Requirement coverage (linked requirements). This full traceability matrix ensures every requirement is tested and every test can be traced back to requirements.

The Test Lab module is specifically designed for test execution, where you create test sets, schedule runs, and execute test cases. Test Plan is for designing tests, not running them.

In Quality Center's Test Plan module, you create the test plan tree by manually defining folders to organize tests and then creating individual tests within those folders. This hierarchical structure organizes your test repository.

Requirement traceability is the process of documenting the relationships between requirements, as well as between requirements and other artifacts like tests or design documents, to track dependencies.