Share this page

# Work with OpenText Functional Testing for Developers automation

This section describes methods for automating components with OpenText Functional Testing for Developers implementation.

Note:

- This task is part of a higher-level task. For details, see Work with Business Process Testing.

- For a sample workflow of using Business Process Testing and keyword GUI automation together, see Work with OpenText Functional Testing.

In this topic:

## Automation overview

OpenText Functional Testing for Developers automated components are reusable modules that perform a specific task when testing your application. This implementation can be viewed and edited both in OpenText Application Quality Management and in OpenText Functional Testing for Developers.

OpenText Functional Testing for Developers is a powerful and lightweight functional testing solution built specifically for continuous testing and continuous integration. By supporting the most common AUT technologies and integrating with standard IDEs, OpenText Functional Testing for Developers brings a new level of productivity and collaboration to your Agile and DevOps testing teams.

OpenText Functional Testing for Developers tests and components using Business Process Testing is supported. You can create OpenText Functional Testing for Developers tests and use all the standard tracking and traceability features to manage them.

You can import tests and components from OpenText Functional Testing for Developers and also initiate runs of OpenText Functional Testing for Developers tests and components from within OpenText Application Quality Management.

You can create OpenText Functional Testing for Developers tests or business components automatically by importing test methods defined in your NUnit or JUnit project.

Alternatively, you can create each OpenText Functional Testing for Developers test or business component manually within OpenText Application Quality Management.

Back to top

## Manually add automation to a component

You can manually add OpenText Functional Testing for Developers automation to business components.

To manually add OpenText Functional Testing for Developers automation to a business component:

1. Prerequisites:

   - Make sure OpenText Functional Testing for Developers is installed.

   - To be able to debug or run automated OpenText Functional Testing for Developers components, or view test results, make sure that UFT Developer 12.53 or later is installed.

2. Select a component.

   In the Business Components module window, select a component in the component tree.

3. Add OpenText Functional Testing for Developers implementation.

   In the Automation tab, click Add Automation and select UFT Developer. Enter the implementation details, and then the following details.

   UI Element | Description
   --- | ---
   Framework | JUnit or NUnit.
   DLL/JAR Path | The path of the .dll or .jar file containing your test, depending on the framework (NUnit or JUnit). You can specify either a full file path or a relative path.
   Fully Qualified Class Name | The full name of your class including the namespace (NUnit) or package (JUnit). Example:
       com.micro_focus.UFT Developer.end2endtest.myJavaApp
       MyFirstLeanFProject.MySite_ProductSearches
   Test Method Name | The name of the test method that this OpenText Application Quality Management test will run.

4. Parameterize components.

   To expand the scope of your UFT Developer business components, use variable input and output parameter values components. For details, see Create parameters.

5. Results.

   - The automation of the component is complete.

   - The icon for the component changes from the manual icon to the UFT Developer icon. For icon details, see Business Process Testing Icons.

   - Tests and flows that contain fully automated components can run in an automatic runner without pausing for user input.

     - To run business process tests, add the components to a business process tests.

     - Add the tests to a test set and run as you would any other test.

     - The tests run on the OpenText Functional Testing for Developers machine.

     - When you run a OpenText Functional Testing for Developers test from the Test Lab module, the OpenText Functional Testing for Developers HTML report is stored in OpenText Application Quality Management.

   - For details, see Run business process tests and flows.

Back to top

## Automatically import automation to a component

The import tool enables you to automatically create tests or components for every test method defined in a NUnit or JUnit project, including setting up the relevant parameters.

To import automation to a business component:

1. Prerequisites:

   On your OpenText Functional Testing for Developers computer:

   1. Create a UFT Developer NUnit or JUnit project containing one or more test methods. These test methods can be defined in a single .cs or .java file or in multiple files within the project.

      The test methods can include Business Process Testing input or output parameters. For more details on data driving your ALM tests and components, see the OpenText Functional Testing for Developers Help Center.

   2. Compile the DLL or export the JAR.

   3. Run the relevant export tool command line utility, found in the <OpenText Functional Testing for Developers installation>\Tools\TestExportTool folder.

2. Import components.

   In the Business Process Testing Business Components module in OpenText Application Quality Management, run the import:

   1. Right-click the folder where you want to add your components and click Import UFT Developer Components .

   2. In the Import UFT Developer Components browse dialog box, select the XML file generated with the export utility in UFT Developer and click Open.

      The Import UFT Developer Components dialog box displays the tests it found in the XML file.

   3. Select the components to import and click Import. Then click Close.

      Tip: You can also click Export to File.

   The import automatically creates new components with UFT Developer automation in the selected folder. All required fields are automatically set in the Automation tab, and all input and output parameters are defined in the corresponding Parameters tab.

Back to top

See also:

- Integrating with OpenText Functional Testing for Developers in the OpenText Functional Testing for Developers Help Center
- Prerequisites for working with OpenText Functional Testing for Developers and installation instructions in the OpenText Functional Testing for Developers Help Center

https://admhelp.microfocus.com Application Quality Management 8942
Tips to improve your search results... OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help 26.1 All View Local Help Center View Online Help Center Version: