Software Testing Fundamentals

In VBScript (used by QTP), UBound(array) returns the highest index of an array, which equals length minus one for zero-based arrays. LBound returns the lowest index, typically zero.

Interactions ARE created for Anonymous Callers in CIM, so the statement 'Interaction will not Create for Anonymous Caller' is False. The system does track and create interactions even when the caller is not identified or authenticated.

Verification is the process of checking that we are building the system right - that is, ensuring the system is being built correctly according to specifications and requirements. Validation (option A) is checking that we're building the right system - that it meets user needs. Option C describes a specific organizational approach, not the definition. Option D describes validation, not verification.

Static testing techniques involve examining code and documentation without running the software. Walkthroughs, data flow analysis, and inspections are all static testing techniques. Error guessing is a dynamic testing technique where testers guess likely error conditions based on experience - it requires executing the software.

Identifying and resolving faults during the planning phase is highly cost-effective because requirements and design issues can be corrected before code is written. Fixing defects in later stages like design, execution, or exit criteria review requires significantly more time, effort, and resources.

The requirements phase serves multiple purposes: understanding user needs, freezing (finalizing) requirements, and defining the scope of testing based on those requirements. All these activities happen during requirements gathering and analysis. Options A, B, and C each capture one aspect, making D the comprehensive answer.

The test plan is primarily derived from the project plan, which contains scope, schedule, resources, and risk information needed for test planning. Business plans focus on financial/projection aspects. Support plans are for maintenance. The project plan provides the foundational information for developing an appropriate test strategy.

A Function/Test Matrix (also called a Traceability Matrix) maps test cases to requirements or functions. In many project management and testing frameworks, this matrix serves as a project status report showing coverage progress. The other options are specific report types, while the matrix is a broader status tracking tool.

Defect Management processes typically include defect prevention (through reviews and quality practices), defect tracking/resolution, and management reporting for visibility. Deliverable base-lining is a Configuration Management activity related to version control and change management, not part of the defect management lifecycle.

Software testing typically accounts for 40-50% of total software development costs according to many industry estimates. This includes test planning, design, execution, and maintenance of test artifacts. Option D '40308' is clearly a data entry or OCR error.

Bottom-up integration testing starts with the terminal (lowest-level) modules first, testing them individually before integrating upward. This contrasts with top-down integration which begins with the main or highest-level module. The key phrase 'starting with terminal modules' identifies bottom-up.

Regression testing is performed specifically to verify that modifications, bug fixes, or updates in one part of the code have not adversely affected existing, unchanged features. It does not focus on testing new changes directly, nor is it restricted to automation or UAT.

The statement 'Component testing does not involve regression testing' is false. Component testing absolutely includes regression testing to ensure that changes or fixes to a component don't introduce new defects. The other statements are generally true: component testing is often done by developers, is also called module/isolation testing, and should have planned completion criteria.

Equivalence partitioning is a black box testing technique that divides input data into valid and invalid classes (partitions). It's appropriate for all testing levels - unit, integration, system, and acceptance testing. It's not restricted to developers, system testing, or white box techniques.

Test prioritization is primarily about making the best use of limited time. By prioritizing, you ensure the most critical tests are executed first, maximizing value within the available time window. It's not necessarily about shortening time, finding more faults inherently, or just being more effective - it's about optimization under constraint.

Ethical Hacking is the formal term for authorized security testing where professionals simulate attacks to identify vulnerabilities. It's commonly known as Penetration Testing (or pen testing). 'Malicious Hacking' is the opposite - unauthorized attacks. Integration testing is a completely different software testing activity.

Cyclomatic Complexity is a structural metric calculated from the control flow graph of code (based on nodes, edges, and connected components). Since it requires knowledge of code structure and control flow, it's fundamentally a white box testing technique used for code coverage analysis and complexity measurement.

Option B states 'Testing can prove that there are no defects' which is INCORRECT. This is a fundamental principle in software testing: testing can never prove the complete absence of defects. Testing can only show the presence of defects (option A), reduce probability of undiscovered errors (option C), but cannot guarantee zero defects (option D). The question asks for the incorrect statement, so B is the correct choice.

Statement Coverage is a white-box testing technique that requires examining the internal code structure to ensure each statement is executed. Black-box testing techniques (equivalence partitioning, boundary value analysis, decision tables) focus on inputs and outputs without seeing the code. Therefore, Statement Coverage does not come under black-box testing.

The Pesticide Paradox in software testing states that if the same tests are repeated repeatedly, eventually they will no longer find new defects because the software becomes 'immune' to those specific tests. To combat this, test cases must be regularly revised and reviewed to discover new defects. Options A and B describe other testing activities, while D is too vague.