Software Testing Fundamentals

Regression testing is performed to verify that modifications or bug fixes have not introduced new defects in unchanged areas of the software.

A failure is the observable departure from specified behavior - when the system doesn't work as expected. An error is a human mistake (option D), a defect is the code flaw (option C), and failures result from defects executing.

Quality is conformance to requirements (Crosby's definition). Option B is impossible - zero defects is not realistic. Option A is a slogan, not a definition. Option D ignores user needs.

Software testing provides confidence to stakeholders about system quality and fitness for use. Option B is wrong because software cannot be guaranteed bug-free. Option C is unrealistic and option D is incomplete.

Functional system testing tests end-to-end functionality of the complete system. Option A describes interoperability testing. Option B describes integration testing. Option D describes performance testing.

UAT stands for User Acceptance Testing - the final testing phase where actual users validate that the system meets business requirements before go-live.

When introducing a new testing tool, it is best practice to pilot it with a small, dedicated team to establish guidelines, best practices, and evaluate its suitability before rolling it out to everyone.

Boundary value analysis is a Black Box testing technique that tests at the boundaries of input domains (e.g., min, min+1, max-1, max) without knowledge of internal code structure.

Quality Control measures product quality, is a specific corrective part of QA procedures, applies to particular products, and deals with the product itself. All these statements describe QC accurately.

AdHoc testing is an informal, unstructured testing approach that falls under Exploratory Testing. It involves simultaneous learning, test design, and execution without formal documentation.

AdHoc testing is an informal, unstructured testing approach that falls under Exploratory Testing. It involves simultaneous learning, test design, and execution without formal documentation. (Duplicate of 137125)

Integration is one of the key process areas at CMM Level 3 (Defined Level). At this level, organizations establish standard processes for software engineering, and Integration specifically addresses integrating software components into a cohesive product.

Equivalence partitioning is a black-box testing technique that divides input data into valid and invalid equivalence classes. Top Down and Bottom Up are white-box integration testing approaches, not black-box methods.

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.

A defect is indeed defined as a variation between the expected result and actual result. When actual output differs from expected output, a defect exists. This is a fundamental definition in software quality assurance.

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.