PowerServer 2021 Help
Load testing installable cloud apps with JMeter

To create a new test plan, select File > New. Input a name for the test plan.

When the test plan is created, it is added to the tree on the left panel. All subsequent elements will be added to this tree in a hierarchical structure.

A Test Plan must have at least one thread group. The Thread Group tells JMeter the number of users (threads) you want to simulate, how often users should send requests and how many requests they should send.

To add a Thread Group to the test plan, right click on the test plan that you added just now, and then select Add > Threads (Users) > Thread Group.

You will need to configure the following properties:

After you created the test plan and a thread group, you can determine which type of requests to make (such as Web (HTTP/HTTPS), FTP, JDBC, Java etc.)

In this test, you need to make the HTTP request to the PowerServer Web APIs.

To add an HTTP request, right click on the thread group that you added just now, and then select Add > Sampler > HTTP Request.

When you specify an HTTP Request, you can make use of the information obtained by Fiddler, such as the protocol, server IP, port, HTTP method, path, body data etc.

For example, you can add an HTTP POST request that access the RetrieveWithParm Web API, and input the JSON request body to the Body Data tab.

In the same way, you can add requests like GET, POST, PUT, and DELETE.

In case you have any specific headers that should be part of the HTTP request, you can add an HTTP header manager. The HTTP header manager lets you add or override HTTP request headers.

To add an HTTP header manager, right click on the HTTP request that you added just now, and then select Add > Config Element > HTTP Header Manager.

When you specify the HTTP header, you can make use of the information obtained by Fiddler.

For example, you can add the Content-Type and Accept-Encoding to the HTTP header manager.

If all requests will use the same header information, you can use one HTTP Header Manager for all requests (or even for all thread groups), instead of each request having its own HTTP Header Manager. You can adjust the hierarchical level of the HTTP Header Manager (by drag & drop) in Thread Group.

The above is basically everything you need as a minimum setup of an HTTP request suite.

However, in order for you to view the results and statistics of the test, you need to add Listeners. There are several types of listeners such as view results tree, summary report, graph results etc.

You can add one or more listeners according to your needs.

To add a listener, right click on the thread group, select Add > Listener, and then choose the listener.

It is recommended that you save the Test Plan to a file before running it.

To save the Test Plan, select Save or Save Test Plan As… from the File menu. The test scripts will be saved in a JMX file. You can then add this file to your project repository, and other members of your team can load it on their own JMeter tools as well.

Now you can start the test by clicking the Start button on the toolbar. This will start the thread group and the results will be captured by the listener.

To run the test again, clean up the previous result by clicking the Clear All button on the toolbar.

Use the various listeners to check the test results.

For example, the View Result Tree is the most commonly used listener which shows all the details related to the request, HTTP headers, body size, response code etc.

You can check if the session ID and the transaction ID are dynamic values in the request body, and use the code returned in the response data to check if the execution is successful or diagnose the error (if any).

The View Result Tree in Table listener displays the information of the request in the form of a table, and in the order of time each request is made.

You can easily find out whether the requests are made simultaneously at the same point of time (for example, when Synchronizing Timer is added).

The Summary Report listener displays the performance matrices of each request, such as the number of samples processed, the average response time, throughput, error rate etc.

To add a setUp Thread Group to the test plan, right click on the test plan that you added just now, and then select Add > Threads (Users) > setUp Thread Group.

Make sure this setUp Thread Group is listed as the first thread group under the test plan, so it starts before the other thread groups. You can drag the item in the tree to adjust their level and order.

You can use the default settings for the setUp Thread Group.

Now you can move (by drag & drop) the following HTTP requests from Thread Group to the setUp Thread Group.

To correlate the session ID, you can first add a Regular Expression Extractor to save the session ID to a local variable; and then add a BeanShell PostProcessor to set the local variable as a global property, so that it can be shared in all thread groups.

To add a Regular Expression Extractor, right click on the CreateSession request and then select Add > Post Processors > Regular Expression Extractor.

Specify the Regular Expression Extractor like this.

The session ID will be saved to the “session” variable.

To add a BeanShell PostProcessor, right click on the CreateSession request, and then select Add > Post Processors > BeanShell PostProcessor.

Input the following script: ${__setProperty(session,${session},)}

The “session” variable can be accessed as a JMeter global property.

Use the Search menu to search for all occurrences of “session” in all thread groups, and then replace the static value of session ID with the global property ${__property(session,,)}.

Similar to the session ID, you can first add a Regular Expression Extractor to save the transaction ID into a local variable; and then add a BeanShell PostProcessor to set the local variable as a global property, so that it can be shared in all thread groups.

To add a Regular Expression Extractor, right click on the ConnectAndCreateTransaction request and then select Add > Post Processors > Regular Expression Extractor.

Specify the Regular Expression Extractor like this:

The transaction ID will be saved to the “transaction” variable.

To add a BeanShell PostProcessor, right click on the ConnectAndCreateTransaction request and then select Add > Post Processors > BeanShell PostProcessor.

Input the following script: ${__setProperty(transaction,${transaction},)}

The “transaction” variable can be accessed as a JMeter global property.

Use the Search menu to search for all occurrences of “transactionid” in all thread groups, and then replace the static value of transaction ID with the global property ${__property(transaction,,)}.

To add a tearDown Thread Group to the test plan, right click on the test plan that you added just now, and then select Add > Threads (Users) > tearDown Thread Group.

Make sure this tearDown Thread Group is listed after Thread Group, so it starts when Thread Group has finished.

You can use the default settings for the tearDown Thread Group. Normally the tearDown Thread Group runs only once.

Now you can move (by drag & drop) the following HTTP requests from Thread Group to the setUp Thread Group.

You can first add a Regular Expression Extractor to save the transaction ID into a local variable; and then add a BeanShell PostProcessor to set the local variable as a global property, so that it can be shared in all thread groups.

To add a Regular Expression Extractor, right click on the CommitAndCreateTransaction request and then select Add > Post Processors > Regular Expression Extractor.

Specify the Regular Expression Extractor like this:

The transaction ID will be saved to the “transaction” variable.

To add a BeanShell PostProcessor, right click on the CommitAndCreateTransaction request and then select Add > Post Processors > BeanShell PostProcessor.

Input the following script: ${__setProperty(transaction,${transaction},)}

The “transaction” variable can be accessed as a JMeter global property.

Use the Search menu to search for all occurrences of “transactionid” in all thread groups, and then replace the static value of transaction ID with the global property ${__property(transaction,,)}.