Software Testing Fundamentals and Automation

In QTP's Test Settings under the Run tab, the Data Table iteration options specifically control the Global sheet iterations - this defines how many times the entire test runs with different data rows. Local sheet iterations are configured per-action in the Action Call Properties, not in Test Settings. Run-time and Design-time refer to when data is available, not which sheet the iteration settings affect.

Action iterations in QTP are configured in the Action Call Properties dialog, which appears when you right-click an action call and select 'Action Call Properties'. This setting controls how many rows from the action's local data sheet are used when that action is called. Action Settings/Properties typically refer to different configuration screens, while Action Run Settings isn't a standard QTP terminology.

ADO (ActiveX Data Objects) uses Connection objects to establish database connectivity and Recordset objects to manipulate and query the returned data. These two objects form the foundation of ADO database operations - you first connect, then work with recordsets to read or modify data. Fields is a property of Recordset, Execute is a method, and Open/ConnectionString are properties/methods of Connection, not standalone objects.

Programmatic descriptions in QTP/UFT allow you to define object properties directly in code without storing them in the Object Repository. You use descriptive programming syntax to identify objects by their properties at runtime. Deleting objects from repositories would break existing tests, adding objects goes into the repository you're trying to bypass, and there's no simple 'turn off' switch for the Object Repository.

In Quality Center's workflow model, defect addition may be restricted based on project settings, user permissions, and testing lifecycle stage, not universally available from all modules.

In Quality Center, changing projects typically requires logging out of the current project and logging into the new one, rather than switching directly within the same session.

QTP (QuickTest Professional) opens with Keyword View as the default interface; Expert View is an advanced option for users who prefer working directly with VBScript code.

In QTP, while you can create multiple actions within a test, you cannot split an existing action into multiple actions; you must create new actions and manually reorganize the steps.

In testing terminology, a condition represents a specific state, event, or scenario that can be validated through test cases, forming the basis of test design and coverage analysis.

In software testing terminology, failure is defined as deviation from the EXPECTED result, not 'unexpected' result. The phrasing is garbled but the statement as written is incorrect.

After a developer fixes a defect, testers should execute not just the specific test case for that defect but also related test cases to ensure the fix didn't introduce new issues. This is part of regression testing.

Test Analysis and Design is a formal test process phase where requirements and design documents are analyzed to identify test conditions and design test cases. This statement correctly describes activities in that phase.

Pair programming is a collaborative practice from agile methodologies (particularly Extreme Programming), not a formal technique in the sense of inspection or formal verification methods. It's informal compared to formal review techniques.

Defect reports are typically closed by testers after verification that the fix is correct. Developers fix defects but don't close the report - testers verify and close them. Separation of duties prevents developers from marking their own work complete.

Black box testing is a software testing method where the internal structure, design, and implementation of the item being tested are not known to the tester. It focuses entirely on the inputs provided and the resulting outputs.

Test comparators are software testing tools designed to compare actual test execution outputs (such as files, databases, or UI states) against expected results to identify discrepancies.

Retesting checks if a specific defect fix works. Regression testing checks if the fix broke other parts of the system. They are different - retesting is focused on the fixed issue, regression is broader.

Integration testing involves testing the interactions between integrated modules or systems. It can employ both black-box testing (verifying inputs and outputs without seeing internal code) and white-box testing (examining internal logic and code structures). While integration testing is a level of testing rather than a method, it commonly uses both approaches at module interfaces.