Software Testing and Quality Control

Validation confirms that the software meets the business requirements and user needs - answering 'Are we building the right product?' Verification (option A) checks technical specifications. Option C describes unit testing, and option D is vague.

Verification is the process of evaluating software to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase (i.e., confirming it meets technical specifications). Validation confirms it meets business requirements.

This statement is False. A Test Plan is a strategic document describing the scope, approach, resources, and schedule for testing activities. A step-by-step procedure for executing a specific test is called a Test Script or Test Procedure, not a Test Plan.

ETVX stands for Entry criteria, Test, Verification/Validation, and Exit criteria. This is a testing documentation standard defining the conditions for starting tests, test procedures, verification/validation activities, and completion criteria.

Smoke test (or build verification test) is the first system test performed to verify basic functionality. It checks that critical features work before deeper testing. Regression testing is for detecting defects in modified code, not the first test.

Guerilla Testing (or monkey testing) is an ad-hoc, unstructured testing technique where testers or business users quickly and randomly interact with the application to find weaknesses without following predefined test cases.

XP includes all three practices: pair programming (continuous review), extensive code review, and comprehensive unit testing. These together ensure code quality and rapid feedback.

Bugzilla is a widely used, open-source web-based general-purpose defect tracking and bug reporting tool. It is not designed for writing test cases or generating XML.

Mercury Quality Center (now HP ALM) is a comprehensive test management tool that tracks test execution progress, manages test case repositories, and maintains requirements with traceability. All three functions are core features.

In Mercury Quality Center/HP ALM, test cases are authored in the Test Plan tab where they're organized into folders and suites. Test Lab is for execution, Requirements Tab links requirements to tests, and there is no standalone Test Case tab.

A test case is marked BLOCKED when it cannot be executed due to a dependency failure - typically when another test case has failed and blocked the path forward. Being out of scope or lack of time are different statuses (N/A or Not Tested).

When a developer rejects a defect, the tester should review the rejection reason, verify if it's justified, and reopen if they disagree with the developer's assessment. Simply closing without review, or always reopening, are both incorrect approaches.

E2E (End-to-End) test validates complete flow from entry point (Gateway) through external systems (Third Party) and back to entry point. Options A-C are incomplete as they don't return to origin. Only D captures the full round-trip through third-party systems.

Severity measures the extent of impact a defect has on system functionality, user experience, or business operations. It's distinct from priority, which relates to how quickly a fix is needed.