Software Testing and Quality Control

When you create a new test in QTP, it automatically includes a single action by default. You can add more actions later, but the initial test has one. Tests with multiple actions are created by explicitly adding them, not by default.

The Wait statement in QTP pauses test execution for a specified number of seconds. WaitProperty waits for a property value, Sync waits for navigation, and Exit terminates a loop/action. Only Wait creates a simple time-based pause.

Checkpoint results are viewed in the Test Results window after a test run completes. This window shows all checkpoint outcomes, screenshots, and pass/fail status. The Checkpoint window is for creating checkpoints, not viewing results.

Reusable actions can be called by other tests or actions, enabling modularity and code reuse. You call them using the 'Call to Copy' or 'Call to Existing' options. Split actions divide an action, Non-reusable actions cannot be called externally.

Low-Level recording mode captures mouse clicks and keyboard input at screen coordinates when QTP cannot recognize an object using standard identification. It works around unrecognized objects by recording raw input actions instead of object-based operations. Normal recording requires object recognition, while Low-Level provides a fallback for difficult-to-identify objects.

The Object Repository is the central storage location where QTP maintains test objects along with their identification properties and corresponding values. It enables QTP to recognize and interact with application objects during test execution by mapping test script references to actual application objects. Other options like Data Table store test data, not object definitions.

F1 is the universal keyboard shortcut for accessing help documentation in most Windows applications, including QuickTest Professional. It launches the context-sensitive help system. F5 is typically for Run/Refresh, F2 for editing, and F3 varies by application but is not standard for help.

QTP maintains a bidirectional relationship between Keyword View and Expert View: every operation in Keyword View corresponds to VBScript code in Expert View, and vice versa. Each object and method call in Expert View generates a corresponding row in Keyword View's table format. This synchronization allows testers to work in either view seamlessly.

A Reusable Action in QTP is specifically designed to be called from other tests or actions, enabling code reuse and modularity. Regular actions are local to their test, but Reusable Actions can be invoked externally with optional parameter passing. Call Action is not a type of action, and Split Action divides an action: it doesn't make it reusable.

GetCellData(Row,Col) is the correct method to retrieve data from an HTML Table in QTP/UFT. The other options (GetData, GetRowValue with various signatures) are not standard methods for table cell extraction.

QTP/UFT allows working with multiple function libraries simultaneously. You can have multiple function library files associated with a test and can edit them concurrently.

QTP tracks execution time for each action within a test. You can view timing information in the Test Results window or programmatically access it through Reporter.ReportEvent or internal properties.

Different test stages have distinct objectives: unit testing verifies individual components, integration testing checks interfaces, system testing validates the complete system, and acceptance testing confirms business requirements. Each stage serves a unique purpose.

Regression testing benefits most from capture/replay tools because it involves repeatedly executing the same tests after changes. Capture/replay allows quick re-execution of existing test suites without manual recreation, making it ideal for regression cycles.