Get started

This topic introduces OpenText™ Enterprise Performance Engineering and provides some tips about getting started.

First steps

OpenText Enterprise Performance Engineering is a cross-enterprise tool for planning and running multiple performance test projects. It enables you to remotely monitor concurrent tests across different geographic locations.

Benefits

OpenText Enterprise Performance Engineering provides the following benefits:

  • Ability to run multiple tests simultaneously, and share test assets across the project

  • Web-based, 24/7, globally accessible platform with centralized resource management

  • DevOps-ready due to its REST APIs, CI plug-ins, and APM tool integrations (Dynatrace SaaS/Managed, New Relic, AppDynamics, CA APM)

  • Dynamic provisioning using elastic Dockerized and cloud-based load generators

  • Smart analytics, including anomaly detection during a test run

  • Integrates with other OpenText products including OpenText Software Delivery Management, SiteScope, and OpenText Functional Testing Lab for Mobile and Web

Light bulb

Discover how you can test the performance of your applications:

  1. Create and run scripts that use virtual users, or Vusers, to emulate typical user activity.

  2. Vusers generate load on your web servers or applications.

  3. While Vusers run, server response time data is collected.

  4. The data is analyzed and provides a clear picture of performance.

Back to top

End-to-end workflow

Following are the basic steps for creating and developing a performance test.

Step Action
Create test assets

1. Create test assets

Create test assets such as a script or a monitor to use in your performance test. For details, see Assets.

Design a test

2. Design a test

Create a test by selecting the test assets to use and defining a workload for the test. For details, see Tests.

Reserve timeslots

3. Reserve a timeslot

Create a timeslot for the test and make sure the timeslot is available. For details, see Reserve timeslots.

Run the tests

4. Run the test

Run the test to create load on your application and to test its performance. During the test run, you can view and manage test runs and results, Vusers, monitors, and load generators. For details, see Run performance tests.

View and Analyze

5. View and analyze test results

View test data in real time or offline, and use built-in tools to analyze test results such as trend reports and anomaly detection. For details, see View and analyze test results.

Back to top

Learn more

Tutorial

Take the tutorial

Follow the steps in the Quick Start Guide to learn how to create and run a performance test.

Watch videos

Watch videos

Learn more about how you can incorporate OpenText Enterprise Performance Engineering into your testing environment by watching demo videos.

Initial setup

Initial setup

Before users can work, administrators need to install and configure OpenText Enterprise Performance Engineering. For details, see Install and Administration basics.

Let's Go button

Let's go!

When you're ready to begin, go to your landing page (http://<server name>/<tenant>), and log on to the standard user or administrator area. For details, see Admin log on and display customization.

For more resources and insights, see the OpenText Performance Engineering page.

Back to top

Integrate with OpenText Core Software Delivery Platform

Note: This feature is offered in a SaaS environment only.

OpenText Enterprise Performance Engineering is part of the OpenText Core Software Delivery Platform module.

You can stream your OpenText Enterprise Performance Engineering performance results to OpenText Core Software Delivery Platform so that you can see a comprehensive picture of your application's quality and coverage in one place.

For details, see OpenText Core Software Delivery Platform integration.

Back to top

Bookmark the Help Center

Bookmark the Help

To ensure that you're always viewing the most up-to-date version of the Help Center, bookmark this link: https://admhelp.microfocus.com/lre.

To create a link that always points to the most recent version of a topic, replace the version number in the URL with 'latest'. For example:

  • Previous version:

    https://admhelp.microfocus.com/lre/en/25.1/online_help/Content/PC/Dashboard.htm

  • Current version:

    https://admhelp.microfocus.com/lre/en/latest/online_help/Content/PC/Dashboard.htm

Back to top

See also: