Automated testing flow

For some of your testing of your application's development, you may use an automated testing tool, like UFT, whether to test your application's user interface and back end, or overall performance.

In cases like this, you can integrate your tests and test results with ALM Octane. This enables you to collect the results from UFT's tests, and use these results to measure overall progress and quality.

This flow describes how to get started using UFT with ALM Octane.

Plan your testing infrastructure

When you decide to use UFT with ALM Octane, you have to decide how you want to manage the test infrastructure. This includes a number of different items:

Where do you save your tests?

UFT enables you to store your tests in a number of places: the local file system, a SCM repository that uses GIT or SVN, or ALM.

While this does not affect how ALM Octane receives and processes the results, it does affect how you structure the flow and test run environment.

How do you package your tests? UFT tests can be structured in a variety of ways: individual tests aimed at a specific functionality, a single end-to-end test that calls other tests, or tests grouped together in test batches.
How do you want ALM Octane to use the UFT test results?

Depending on how you want ALM Octane to use the results, you have different options:

  • If you have individual tests that you want evaluated separately, you can send the results to ALM Octane individually.

  • If you have a group of tests or a test batch aimed at a more comprehensive or end-to-end test of your application under test, you can have them be evaluated as a test suite in ALM Octane.

Answering these questions enables you to better structure your test runs and your tests in ALM Octane to gain the maximum insight from UFT test runs

Back to top

Set up your test run environment

In order to run UFT automated testing tools test and enable ALM Octane to use the results from the test run, you need to create the test run environment.

This is done through running a job on a Jenkins CI server.

Although the tests are run via the CI server, there is no need to have a full CI system in place.

Preparing the Jenkins environment requires a few actions:

Back to top

Prepare your UFT test environment

In addition to preparing your test run environment, you must also prepare UFT environment.

This includes:

  • Installing UFT on the same computer with the Jenkins CI server/Jenkins slave machine server

  • Installing and loading the necessary add-ins for UFT

  • Ensuring the application under test is accessible from the UFT computer

  • If you are working with tests saved in ALM, ensuring that the ALM server is accessible

    Note: It is recommended to connect to ALM at least once with administrative privileges from UFT on the computer running the tests in UFT. This ensures that all ALM components are downloaded and configured correctly before you begin a test run.

Back to top

Create a Jenkins project to run UFT tests

After you have set up both Jenkins and UFT, you are ready to create the Jenkins build projects that enable you to run the tests and pass the results to ALM Octane. This process helps you perform the entire process with one click.

Jenkins job setup can require any of the following:

Back to top

Run the pipeline and collect results

In order for ALM Octane to collect and use the UFT test results, the Jenkins jobs must be included in a pipeline run.

You can create these pipelines from ALM Octane or from the Jenkins project:

You can run this pipeline in a number of ways:

  • Run the pipeline from ALM Octane simply by pressing the Run Pipeline button in the Pipelines module

  • Launch the project in Jenkins manually

  • Schedule the build project in Jenkins to run at a pre-determined time.

Note: For UFT tests: Ensure that your application is in the necessary state before running the pipeline as specified in the Record and Run Settings of your UFT tests.

After the pipeline (and by extension, test) run is finished, the plugin collects the test results and passes them to ALM Octane.

For details on creating and working with pipelines, see Pipelines: CI server & SCM system integration.

How does ALM Octane know where to put the test results?

As you know, when creating tests in ALM Octane, you can only select from ALM Octane's native test types: Manual or Gherkin tests. In turn, these tests are edited from within ALM Octane (except for Gherkin tests which can be edited in an external IDE). Neither of these test types are a UFT test or can be used by UFT.

However, when you run a build project containing tests from UFT other automated testing tools, the results are sent to ALM Octane, and ALM Octane decides accordingly how to treat them:

  • If the test results are similar to an existing test, they are assigned to that test as one of the test's runs.

  • If the test results are not similar to any existing test in the system, ALM Octane creates a new test and provides the details from the test results. This test is then displayed in the tests grid in the Backlog module and Quality modules.

The tests can then be assigned to application modules, and the results factor into dashboard analysis of progress and quality.

For details on this automatic assignment, see Add automated tests.

Back to top

Use test assignment rules to connect results

After you collect the test results in ALM Octane and assign them to the appropriate application modules, ALM Octane provides an additional powerful tool to enable you to continuously use the test results s a part of your analysis.

By setting test assignment rules that automatically distribute the test run results to the appropriate locations after the test runs, ALM Octane creates the framework for you to continously use your UFT test results as part of evaluating your application's progress and quality.

For details, see Create and manage test assignment rules.

Back to top