Set up your system

• On any machine on which you want to run tests, install the OpenText Functional Testing for Developers runtime engine. For details, see Installation guide.
• On any machine on which you want to write and edit tests, install one or more supported IDEs and the IDE plugin included in the OpenText Functional Testing for Developers installation.

• Customize the runtime engine settings
• For Web testing, see Set up web browsers and controls.
• Customize how to identify objects
• Modify the communication port number
• Configure ports for a multi-session environment

Create a testing project

Create a testing project in the IDE of your choice, using the provided project templates, or use your own custom framework.

See Create a testing project or module.

Customize your test settings

Customize the runtime engine settings and report options.

See Customize test settings

Define test objects

Create test object descriptions that enable OpenText Functional Testing for Developers to identify the objects in your application and can withstand changes in the application you’re testing.

Write programmatic descriptions or use the visually oriented tools that OpenText Functional Testing for Developers offers to provide an interface to the tested application and its objects.

For details, see:

• Code programmatic test object descriptions
• Object Identification Center lets you spy on the objects in your application, experiment with different ways to identify those objects, and generate code to use in your scripts.
• Application models are abstractions, or models, of the application you are testing.

Write tests

After you create test object descriptions, write automated tests whose steps call the methods and properties of these OpenText Functional Testing for Developers test objects.

Use one or more of the following SDKs:

• .NET SDK

• Java SDK

• JavaScript SDK

Use the Test Recorder to accelerate test creation, recording user operations on the tested application and generating a test script from the recorded steps.

Add code to verify application behavior

Verify that the objects in your application look and behave as you expect.

When these special steps return false results, the step and test fail, but no exception is thrown and your test continues to run.

For details, see Verifications.

Run test

Run your tests in Jenkins or other tools as part of your CI/CD processes. See Run tests.

Analyze run results

HTML reports include information about the run, including optional screen captures. See Analyze run results.