Working with functional test scripts (Windows-only)
This section
describes the process of creating functional test scripts to test
your applications.
- Working with simplified scripting
- Working with Java test scripts
- Using script services
The Script Support Functions dialog box contains tabs that enable you to insert code into the current Functional Test script to perform a variety of tasks, such as inserting a callScript command, a log message. a timer, a sleep command, or a comment into a Functional Test script. - Starting your test applications
When recording tests on your application, it is best to have HCL OneTest™ UI start the application during recording. This makes playing back the tests more reliable because the application configuration information is used. HCL OneTest UI can open specified Java applications, HTML pages in your browser, or run executable applications. - Renaming a test asset
You can rename simplified test scripts, Java test scripts, test object maps, or other files in a project. - Saving test scripts and files
- Saving a test script with another name
- Saving a file with another name
- Deleting a functional test script
You can delete a functional test script from the Projects view or the Solution Explorer. Use caution, however; deleting a script that is not under ClearCase® source control or a script in a ClearCase dynamic view cannot be undone. - Tips for recording functional tests
Following are some tips on ways around some potential recording issues. - Recording a script
To start recording scripts against your applications, you must first configure your test environments, configure your applications, and create a project. Under certain conditions, you can start recording scripts without preparing your functional test environment. - Creating a new test script without recording
As an alternative to recording, you can create a script to enter VB.NET code manually. - Recording in an existing script
In a functional test script, you can start recording at the cursor location. By starting to record in a script, you can start applications, insert verification points, and add script support functions. - Recording scripts to test HTML applications
Record scripts to test HTML applications on a single browser as you record any functional test script. - Recording cross-browser and cross-platform scripts
This topic provides an overview of the procedures to set up your environment to record cross-browser scripts. - Displaying test object information
You use the Test Object Inspector to examine graphical components visible in the running application and display information about those objects, such as parent hierarchy, inheritance hierarchy, test object properties, non value properties, and method information. - Getting a property value
You can get a single property value for the selected object while you are recording. It puts a getProperty into your script and returns the value during playback. - Setting a wait state for an object
This feature is used to set a wait state for an object during playback to check for its existence. This is useful when waiting for an object right after starting your application, or after other actions that may take a long time. - Changing the default script helper base class for a script
You can change the script helper base class for an individual script. - Recording and playing back double byte characters on Chinese systems
The following information pertains to record and playback of DBCS on Chinese systems. - Working with verification points
Verification points verify that a certain action has taken place, or verify the state of a control or an object. When you create a verification point, you are capturing information about a control or an object in the application to establish this as baseline information for comparison during playback. - Working with simplified scripting
- Working with Java test scripts
- Using script services
The Script Support Functions dialog box contains tabs that enable you to insert code into the current Functional Test script to perform a variety of tasks, such as inserting a callScript command, a log message. a timer, a sleep command, or a comment into a Functional Test script. - Starting your test applications
When recording tests on your application, it is best to have HCL OneTest UI start the application during recording. This makes playing back the tests more reliable because the application configuration information is used. HCL OneTest UI can open specified Java applications, HTML pages in your browser, or run executable applications. - Renaming a test asset
You can rename simplified test scripts, Java test scripts, test object maps, or other files in a project. - Saving test scripts and files
- Saving a test script with another name
- Saving a file with another name
- Deleting a functional test script
You can delete a functional test script from the Projects view or the Solution Explorer. Use caution, however; deleting a script that is not under ClearCase source control or a script in a ClearCase dynamic view cannot be undone. - Tips for recording functional tests
Following are some tips on ways around some potential recording issues. - Recording a script
To start recording scripts against your applications, you must first configure your test environments, configure your applications, and create a project. Under certain conditions, you can start recording scripts without preparing your functional test environment.