Software Testing and QTP Fundamentals

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.

In QTP (QuickTest Professional), files with the .tsr extension represent shared object repositories. Other options like .vbs are action/script files, and data is typically stored in Excel .xls or .xlsx files.

Getrowcount is the standard method to retrieve the number of rows in a table object in QTP. Getlinecount typically refers to line counting, count is a generic term, and Getcount is not the standard QTP method for row enumeration.

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.

WaitProperty is the synchronization method that waits for a specific object property to reach a desired value. Synchronize is a general term, Wait introduces a fixed delay, and Pause halts execution without property-based waiting.

QTP supports adding external library files through the Associate Repository feature or using the ExecuteFile method. This allows testers to reuse code functions across multiple tests, improving maintainability and reducing redundancy.

Boundary value analysis is a black-box testing technique that focuses on testing at the boundaries, just below, and just above the edges of input and output equivalence classes. It's distinct from equivalence partitioning (A), doesn't test combinations (C), and is not specific to white-box testing (D).

Non-functional testing evaluates system attributes beyond functional behavior. Usability testing assesses user experience and interface design, while Performance testing measures system responsiveness, scalability, and speed under load. Both test quality characteristics rather than specific features.

Capture/Playback tools record manual test interactions and replay them automatically, making them ideal for regression test automation. They capture user actions and test inputs during manual execution, then reproduce them precisely to validate that recent changes haven't broken existing functionality.

Independent Verification & Validation means testing performed by an organization completely separate from the development project. This independence ensures objectivity - the evaluating entity has no stake in the project's outcome and no influence from the development team, providing unbiased quality assessment.

Maintenance testing involves testing a system that has already been released and is operational, after changes or modifications have been made. It ensures that updates, patches, or enhancements haven't introduced defects and that the system continues to function correctly in its production environment.

Beta testing is performed by actual end users at their own locations using their own hardware and data. This distinguishes it from alpha testing, which is conducted at the developer's site by internal teams. Beta testing provides real-world validation before general release.

Re-testing (confirmation testing) is performed to verify that a specific bug has been successfully resolved. Regression testing checks whether recent code modifications have accidentally introduced new faults or broken existing functionality in unmodified areas of the system. Their purposes and scopes are distinct.

Fixing a fault later in the software development lifecycle increases costs exponentially because it requires rework of designs, code, and testing phases already completed. Finding a defect during development or requirements phase is cheapest, making late discovery much more expensive than early detection.