Home
Test Author Guide
This guide describes how to create test scripts and enhances them by applying different test elements such as dataset, variables, and verification points.
Extending the UI Test perspective with custom Java™ code
You can use custom code to extend the default Web UI testing capabilities. You can write custom Java™ code and call the code from the test. You can also specify that results from the tests that are affected by your custom code to be included in reports.
Migrating custom code from previous versions
You can run scripts that contain custom code from previous releases and edit tests to make new calls to the old or new custom code classes.

Test Author Guide
This guide describes how to create test scripts and enhances them by applying different test elements such as dataset, variables, and verification points.
- Tests in the UI Test perspective
  When you develop web applications, Windows-based applications, or mobile applications, you can use HCL DevOps Test UI (Test UI) to create functional tests for these applications. You must first record the tests and then use Test UI to run the tests before you can view the test results.
- Tests in the Functional Test perspective
  When you develop Java, HTML, or Terminal-based applications, you can use HCL DevOps Test UI (Test UI) to create traditional functional tests for these applications. You must first record the tests and then use Test UI to run the tests before you can view the test results.
- Extending the UI Test perspective with custom Java™ code
  You can use custom code to extend the default Web UI testing capabilities. You can write custom Java™ code and call the code from the test. You can also specify that results from the tests that are affected by your custom code to be included in reports.
  - Creating custom Java™ code
    You can create custom code that uses references in the test as input and returns modified values to the test.
  - Test execution services interfaces and classes
    You can use the test execution services interfaces and classes to customize how you run tests. These interfaces and classes are located in the com.ibm.rational.test.lt.kernel package.
  - Performance impact of custom Java™ code
    You can reduce the performance impact of custom Java™ code that is inserted inside a page. The response time of the page is affected if custom code runs inside a page.
  - Custom Java™ code examples
    Custom code enables you to perform such tasks as managing loops, retrieving virtual user information, running external programs from tests, and customizing data correlation.
  - Debugging custom code
    You can debug custom code by adding a breakpoint. This way of debugging custom code is applicable only for a schedule.
  - Migrating custom code from previous versions
    You can run scripts that contain custom code from previous releases and edit tests to make new calls to the old or new custom code classes.
- Extending the Functional Test perspective
  You can use custom code to extend the default functional testing capabilities. You can write custom code and call the code from the test. You can also specify that results from the tests that are affected by your custom code to be included in reports.
- Extending the functionality in the Visual Studio IDE
  These topics describe various ways that you can customize HCL DevOps Test UI (Test UI) or use the application programming interface (API) to extend Test UI functionality.
- Experimental features
  HCL DevOps Test UI (Test UI) contains a set of pre-releases that enable you to test various experimental features. These experimental features, while still in progress, are introduced early in the release to seek your feedback on its overall functionality and performance. You can play around with these capabilities before they are made available and supported as a general feature in an upcoming release.

Migrating custom code from previous versions

You can run scripts that contain custom code from previous releases and edit tests to make new calls to the old or new custom code classes.

About this task

When you migrate the custom code from the previous versions, you must use getStatisticsManager2() as getStatisticsManager() API is deprecated from 10.1.0.

To edit a class in existing custom code so that it can call new TestExecutionServices methods, you must type cast the IKlog argument in the old custom code to the ITestExecutionServices interface.

Run a script that contains custom code that was created in a previous release.
Edit a test to make a new call to an old custom code class.
Add new custom code to a test that contains the old custom code.