Software Testing and Quality Control

A deferred defect is a confirmed defect that is documented but intentionally not fixed immediately - it will be addressed later in the project. This might happen due to time constraints, low priority, or plans to fix it during a later phase. Option A is technically true but too vague. Option B describes a defect needing clarification, not deferral. Option D is incorrect - it IS a defect, just postponed.

In TMF, a Test Account provides the credentials (username and password) used when executing test requests. This allows tests to run against systems requiring authentication. The key word is executing - not creating, deleting, or separately testing the request.

Penetration testing involves actively exploiting vulnerabilities to identify security weaknesses in hardware, software, or configurations. Unlike vulnerability assessment (option B), which identifies potential issues, pentesting demonstrates their impact through exploitation. Options A and C are generic terms that don't specifically involve exploiting vulnerabilities.

The correct testing order is Unit → Module → Integration → System → User Acceptance. Integration testing must occur BEFORE System level testing because you need integrated modules before you can test the complete system. The given order places Integration after System, which is incorrect.

Installation Testing specifically involves verifying that the software installs correctly according to installation documentation and manuals, and that all installation steps, prerequisites, and configuration requirements are properly documented and followed.

BAT, Verification, and Sanity testing are related types of preliminary testing performed to ensure basic functionality. Validation testing is the odd one out because it's a broader concept checking if the software meets user needs and requirements, not just a preliminary smoke test.

The question asks which statement is WRONG. Option C is incorrect because GUI and database testing are dynamic, but syntax checking and structure investigation are static analysis techniques, not dynamic testing. Volume testing tests performance with large data volumes (not primarily functionality), and regression testing is not exclusively a white-box technique.

Regression testing is testing performed after code modifications to verify that existing functionality remains unaffected. It selectively retests parts of the system that could be impacted by the changes. Option C correctly describes it as testing that uncovers errors by partially retesting a modified program.

This is a duplicate of question 152336. Regression testing is testing performed after code modifications to verify that existing functionality remains unaffected. It selectively retests parts of the system that could be impacted by the changes.

QTP's Active Screen technology captures screenshots of the application under test (AUT) as they appeared during recording. These screenshots help users insert checkpoints and parameterize objects directly from the captured UI.

Parameterization is the feature of selecting different test data values at run-time. It allows tests to use data-driven inputs from external sources (data tables, Excel, databases) instead of hardcoded values, enabling the same test to run with multiple data sets.

A Recovery Scenario in HP QuickTest Professional (QTP) is designed to handle unpredictable errors and testing exceptions during execution. Standard control statements like Do Loop or IF cannot handle unexpected popups.

The Const statement is used to declare constants in QTP (VBScript syntax). Dim declares variables, Con is not a valid statement, and Option Explicit forces variable declaration but doesn't create constants.

Low-Level Recording mode is specifically used when QuickTest cannot recognize an object during recording. It records at the coordinate level. Analog mode is for continuous mouse/keyboard operations, Normal mode is standard recording, and Run Analog is not a recording mode type.

A Reusable Action can be called by other tests or actions in QTP, enabling code modularity and reusability. Call Action is a command, Split Action divides actions, and Called action is not the formal term for this capability.