testing Online Quiz - 164

Beta testing involves testing the software at the client's site after installation, allowing real users to provide feedback before final release. Compatibility testing checks if the software works across different platforms, ad hoc testing is informal without planning, and accessibility testing ensures usability for disabled users.

In automation tools like Blue Prism or similar RPA platforms, reusable actions are configured through Action Properties. This is where you mark an action as reusable so it can be called from other processes or objects.

The DataTable.Value method is used to retrieve or set data from the Data Table during test execution. While GetCell can also retrieve data, Value is the primary method for parameter-based data access. Import is for loading external files, and GetValue is not a standard DataTable method.

UFT/QTP supports two types of environment variables: Built-in variables (predefined by the tool) and User-defined variables (created by testers). Built-in variables include system information like test path, OS type, and test name. User-defined variables can be added manually and accessed programmatically.

When the Global Data sheet is empty, QTP/UFT runs the test only once regardless of how many rows exist in the Local Data sheet. The test iteration count is determined by the Global sheet, which has zero rows in this case. Local data sheet iterations are per-action and don't affect the overall test iteration count when Global is empty.

By default, an action iterates only once regardless of how many rows exist in its Local Data sheet. To make an action iterate for each row in the Local Data sheet, you must explicitly configure the action's 'Run on all rows' setting. Without this setting, the action runs once using the first row of data.

QTP/UFT provides four main trigger event types for Recovery Scenarios: Pop-up window (unexpected dialog), Object State (property changes), Test run error (script failures), and Application crash (application terminates). These events trigger recovery operations to handle exceptions automatically during test execution. VBScript events are not trigger types in this context.

The Step keyword in VBScript For loops defines how the counter variable increments. Default increment is 1, but Step allows custom increments like Step 2 (count by 2) or Step -1 (count backwards). The Next keyword marks the end of the loop body, ++ is not valid VBScript, and Skip is not a loop keyword.

To properly clean up database resources in VBScript/ADO, you must explicitly call the .Close method on both the RecordSet and Connection objects to terminate the active session.

In VBScript, constants are declared using the Const statement (e.g., Const PI = 3.14). Dim is for variables, Con is not a valid statement, and Option Explicit forces variable declaration but doesn't define constants. Once assigned, constants cannot be modified during script execution.

By default, creating a new action in QTP/UFT automatically generates a Local Object Repository, a Local Data Sheet, and a corresponding folder structure to store the action's assets.

The Step Generator in QTP/UFT organizes available operations into three categories: Test Objects (application objects), Utility Objects (built-in tools like DataTable), and Functions (user-defined or library functions). This categorization helps testers quickly locate the appropriate operation type when generating test steps programmatically.

Recovery Scenarios are specifically designed to handle unpredictable exceptions during testing, such as unexpected pop-ups, crashes, or object state changes. Do Loop is for controlled iteration, IFTHEN is conditional logic, and Select Case handles multiple conditions. Recovery Scenarios provide event-driven exception handling.

Function libraries are associated with tests through the Test Settings dialog, specifically in the Resources tab. Run Options controls execution behavior, View Options affects display settings, and Function Definition Generator helps create functions but doesn't associate libraries to tests.

Output parameter results from test actions are stored in the Run-time Data Table during test execution. This allows accessing dynamic values generated during the test run. Local sheet refers to action-specific data, Global sheet to test-level data, and Design-time table is the static sheet created at design time.

In HP QuickTest Professional (QTP) / Unified Functional Testing (UFT), you can globally disable the recognition and use of Virtual Objects by changing the setting in the General Options dialog.

The Source property of a database checkpoint contains the SQL query that retrieves data for comparison. This query defines which data to fetch from the database for checkpoint validation. The connection string is in ConnectionString property, and the number of rows or ID are not represented by Source.

In QTP/UFT Recovery Scenarios, the Trigger must be defined first as it specifies the event that activates the recovery scenario (e.g., a popup window appears or an application crash). Only after defining the trigger can you specify the recovery operations and other settings. The Recovery Scenario Name and Function definitions come after the trigger is established.

Bitmap checkpoints in QTP/UFT capture and compare screen areas pixel-by-pixel. Screen resolution changes affect pixel density and layout, while image size determines the captured area dimensions. Object type doesn't matter for bitmap comparisons since they're purely visual - it's all about screen pixels. Image type vs object type distinctions aren't relevant to bitmap checkpoint sensitivity.

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.