Scripts are used in Performance Center to emulate real user activities on your application. This topic provides an overview of how to create scripts and upload them to Performance Center to run your performance tests.
When you run a performance test, virtual users (Vusers) access your application concurrently in order to put load on your server. The actual steps that the Vusers perform when accessing your application are represented in a Vuser script. Each Vuser performs the actions recorded in one Vuser script.
You design Vuser scripts to emulate typical end-user activities on your application. For example, if you are testing performance on a Web site, the Vuser script emulates a real user accessing URLs, clicking links, submitting forms, and so on. When you create a performance test, you distribute your Vuser scripts among your Vusers.
Example: In the case of testing a Web site, you can specify that a portion of the Vusers run a Vuser script that emulates real users accessing your home page, a portion run a script that performs a search query, and a portion emulate the completion of an order form.
How do you create scripts?
You can use HPE's Virtual User Generator (VuGen) to record Vuser scripts, and then upload them to Performance Center. For details, see, Upload VuGen Scripts.
You can also obtain scripts by converting existing NUnit, JUnit, or Selenium tests and uploading them to Performance Center, or by uploading JMeter scripts. For details, see, Convert NUnit, JUnit, or Selenium Tests to VuGen Scripts and Upload JMeter Tests.
What environments can you test?
In addition to testing Web sites, Performance Center can be used to test performance of non-Web environments. For example, you can test Citrix, MQTT, or Oracle NCA applications. For details of supported protocols, see the Virtual User Generator Help Center (select the relevant version).
When setting VuGen parameters in a Vuser script, you can define AUT environment parameters. AUT Environments allows users to make test execution more dynamic by parameterizing the environment data used for testing.
Instead of defining and running several different scripts that use the same logic but need different AUT environment parameters, you can simply provide a specific AUT environment configuration that ALM inserts into your script at runtime. ALM will then use the parameter values you defined in the AUT environment configuration when deploying the environment and executing the test.
For more details on working with AUT environments, see the ALM Help Center.