JNTU B.Tech III SOFTWARE TESTING METHODOLOGIES Previous Question Paper (February/March - 2022 - R16)

Testing blindness refers to the phenomenon where a tester fails to identify defects because they are influenced by preconceived notions, assumptions, or a lack of objective perspective. It occurs when a tester sees what they expect to see rather than what is actually present in the software.

Key factors contributing to testing blindness include:

• Developer Bias: When a developer tests their own code, they often unconsciously avoid testing paths that they know are fragile or follow the same logic patterns used during development.
• Test Case Over-familiarity: Repeatedly executing the same test cases can lead to a state where the tester stops looking for subtle anomalies, assuming the system is working correctly because it passed previously.
• Assumption of Correctness: Testers may assume that certain modules are bug-free based on their reputation or previous versions, leading them to overlook critical edge cases in those areas.
• Lack of Domain Knowledge: Without a deep understanding of the business logic, a tester may identify the software as working correctly according to the UI, while missing underlying functional errors.

To mitigate testing blindness, organizations employ strategies such as independent testing teams, peer reviews of test plans, exploratory testing to break routine, and the use of automated tools to ensure consistent, objective coverage.

A model for testing provides a structured framework to guide the testing process from requirements analysis to final delivery. A widely recognized model is the V-Model, which emphasizes the relationship between each phase of development and its corresponding testing phase.

The model consists of the following stages:

• Requirements Analysis: The testing process begins here by defining acceptance criteria and test objectives.
• System Design: System test plans are created based on the system requirements to ensure the high-level architecture meets user needs.
• Architectural Design: Integration test plans are developed to verify the interfaces and communication between different modules.
• Module Design: Unit test cases are designed to validate the internal logic of individual components.
• Coding: The actual implementation occurs, followed by the execution of unit tests.
• Testing Phases: As the development moves up the right side of the V, integration, system, and acceptance testing are performed sequentially to validate the system against the specifications defined on the left side.

The primary advantage of this model is that it ensures test planning happens early in the lifecycle, reducing the cost of fixing defects found later. It promotes a systematic approach where every development artifact has a corresponding verification activity, ensuring high traceability and quality assurance throughout the software development lifecycle.