Share this page

# Creating OpenText Functional Testing tests

When creating test scripts in OpenText Functional Testing that are going to be used as GUI Vuser scripts in a Controller testing scenario, you need to follow certain guidelines to ensure smooth integration of the script.

In this topic:

## Known issues

OpenText Functional Testing offers several features that are designed specifically for integration with OpenText Professional Performance Engineering. Some features, however, may not be available for the integration.

For detailed explanations about creating tests and specific limitations, see the Help Center.

Back to top

## Including transactions

To measure the performance of the server, you define transactions. A transaction represents an action or a set of actions that you are interested in measuring. You define transactions within your Vuser script by enclosing the appropriate sections of the script with start and end transaction statements.

For example, you can define a transaction that measures the time it takes for the server to process a request to view the balance of an account and for the information to be displayed at the ATM.

Note: OpenText Professional Performance Engineering only provides performance information for data that is included within a transaction. Therefore, your test must include transactions.

Back to top

## Adding statements

You can use the Services object and its associated methods to insert statements that are specifically relevant to performance testing. These include Abort, GetEnvironmentAttribute, LogMessage, SetTransactionStatus, ThinkTime, UserDataPoint, StartTransaction and EndTransaction.

Back to top

## Designing tests

Consider the following design guidelines when designing tests for use with OpenText Professional Performance Engineering:

- The OpenText Functional Testing tests should be simple tests, designed to pinpoint specific operations.

- Nested action iterations are not supported.

- Do not include references to external actions or other external resources, such as an external Data Table file, environment variable file, or shared object repositories.

- If you want to run an API load test in OpenText Professional Performance Engineering, make sure it has been converted in OpenText Functional Testing to API Load Test type.

Back to top

https://admhelp.microfocus.com Professional Performance Engineering,VuGen 8942
Tips to improve your search results... OpenText™ Professional Performance Engineering Help Center OpenText™ Professional Performance Engineering Help 26.1 All View Local Help Center View Online Help Center Version: