QTP QuickTest Professional Test Automation

In QTP (QuickTest Pro), the GetCellData(Row, Col) method retrieves data from an HTML table cell by specifying row and column indices. The other options (GetRowValue, GetData, GetCellValue) are not standard QTP methods for table data retrieval. Understanding the correct method is essential for web table testing and validation.

In QTP (QuickTest Professional), transaction operations are invoked through the Services object. The StartTransaction and EndTransaction methods are called on Services with the transaction name as a string argument. This syntax properly marks the beginning and end of a transaction for timing and reporting purposes.

In QTP, the global data sheet can be referenced using either the 'Global' keyword or the 'dtGlobalSheet' object. Both notations provide access to the global data sheet used across multiple actions in a test, though they represent slightly different object models within QTP's data table architecture.

In QTP, when you create a checkpoint, its configuration and properties are stored locally within the action's Local Object Repository (.mtr file).

The Accessibility checkpoint in QTP is designed to verify that a web page complies with W3C accessibility standards (WCAG). It checks for proper HTML structure, ALT text for images, and other accessibility guidelines. Bitmap checkpoints capture pixel-by-pixel appearance, Standard checkpoints verify object properties, and XML checkpoints validate XML structure.

The BeepOnSync property in QTP controls whether the application produces an audible sound after each synchronization point during test execution. When enabled, it provides audio feedback that a Sync operation has completed. This is a QTP setting that can be configured in the Test Settings dialog or programmatically.

The Checkpoint timeout setting in QTP specifies the maximum time duration (in seconds) that QTP will attempt to successfully verify a checkpoint. During this period, QTP retries the checkpoint verification at regular intervals. If the checkpoint cannot be verified within the timeout, the step fails. This applies to all checkpoint types.

This statement uses descriptive programming for the Browser and Page objects using regular expressions (title:=...), and standard repository identification for the child WebEdit object, which is syntactically valid in QTP.

In HP QuickTest Professional (QTP) / Unified Functional Testing (UFT), Shared Object Repositories are saved with the .tsr extension, while Local Object Repositories are saved with the .mtr extension.

When an object cannot be identified by its listed properties, most testing tools allow using a "default property" or ordinal identifier as a fallback mechanism. This typically means identifying the object by its index or position among similar objects (like "the 3rd button on the page"). Adding properties or using other properties would require those properties to be available and reliable.

The OSS_TestExecution Sheet is the central spreadsheet where all components for a specific proposition are listed. This sheet contains an Execute flag (Yes/No) for each component, which determines which component scripts should be executed during the test run. OSS_cfg contains configuration settings, and Inter_TestCase_DataTransition handles data passing between test cases.

The Temp folder is designated to store the output spreadsheets generated by component script execution. This keeps temporary outputs separate from the main Data folder (test data), Reports folder (HTML reports), and Logs folder (execution logs), maintaining clean file organization and preventing clutter in permanent directories.

Log files in the logs folder contain detailed initialization information including whether required files like OSS_TestExecution Sheet and OSS_cfg were loaded successfully. The logs capture any loading errors, file path issues, or initialization failures that might occur when the framework starts up. HTML reports show test results, not initialization status.

OSS_cfg is the configuration file where report output paths are defined. This makes the report paths configurable rather than hardcoded in the scripts, allowing users to change where Detailed and Summary HTML Reports are stored without modifying the test scripts themselves. The OSS_TestExecution Sheet lists components, and Test data Sheet contains input data.

The framework executes only the first component flagged with Yes in the OSS_TestExecution Sheet, then stops after successful execution. Multiple Yes flags do not trigger sequential execution of all flagged components - only the first Yes in the list is processed. This is a design choice to ensure controlled, single-component execution per run.

Both the Scripts and Data folders contain Applications and Common sub-folders. The Scripts folder organizes test scripts into Applications (app-specific tests) and Common (shared/reusable scripts). Similarly, the Data folder organizes test data files into Applications and Common sub-folders for corresponding scripts. Reports has a different structure without these sub-folders.

The OSS_API.vbs file contains the function for loading the Object Repository. This centralizes repository loading logic at the API level rather than duplicating it across each component's .vbs file or placing it in OSS_Main or OSS_DriverScript. The API file provides common functions that components can call as needed.

Components do not each have their own standalone executable files. Instead, components are .vbs script files that are executed by common driver scripts in the framework. The framework uses a modular architecture where driver scripts call component scripts as needed, rather than each component being a separate executable program.

If Inter_TestCase_DataTransition is not deleted before executing a new scenario, the new order details will overwrite the existing data in that sheet. The framework does not auto-delete the existing sheet, nor does it stop execution. It simply writes the new scenario's output data over the previous contents, which can cause data confusion if the old output needs to be preserved.

Each component in the Proposition framework has its own separate .usr and .vbs files. The .usr file typically contains user settings, configurations, or parameters specific to that component, while the .vbs file contains the actual test script logic for the component. This modularity allows each component to be maintained and configured independently.