Run Load Test

Edit Gatling Home Path

  1. Download Gatling v3.6.0.

  2. Go to the Settings configuration page under Administration.

  3. Type your Gatling installation path in Gatling Home Path.

Import a Sample Test Project

  1. Click the Sample Project button in the project tab.

  2. Fill in the import form according to the following table.

    Parameter Description
    Server Server environment
    Process App Process app list of the selected server, default value is “Hiring Sample”
    Selenium Hub Support Chrome, Firefox Selenium node

  3. Click the Import button.

  4. Click _Hring Sample from the project list and enter the project dashboard.

    The default sample project contains two suites: Create Position Request CSHS and Standard HR Open New Position.

Edit Engine Properties

  1. Click the Edit button to edit the project.

  2. Click Advance and type the following parameter in Engine Properties:

Replay a Test Case

  1. Click the project name to get into the project, click the case1 under the Create Position Request CSHS package. Click the Record button on the right of the case name to replay it.

  2. Do not click button. Let it run from the first step to the last step.

  3. In the Debug step, which has in front of it, the recording will be stopped. You need to click button to resume.

  4. When all the steps are finished, the recorder will automatically close, and there will be an extra button on the page named Load Test. The Load Test button is only displayed after the test case is replayed from the first to the last step.

Run Test Case Load Test

  1. Click the Load Test button on the right of the case name.

  2. A strategy selection window will pop up. Here, we use the atOnceUsers strategy and set the proper number of users.

    We provide two strategies for usage:

    • atOnceUsers(nbUsers): Injects a given number of users at once.
    • rampUsers(nbUsers) during(duration): Injects a given number of users distributed evenly on a time window of a given duration.

    In the Advanced tab:

    • Change the default assertion value to meet the load case scenario statistics. If any assertion fails, the whole load test case will fail.
    • Change the log level for the load testing. You can download the load testing log in the Performance Report tab page.
    • Switch on Check BAW Product Requests to include BAW product internal requests (i.e., JS/CSS/Image resources and Portal requests loaded by BAW) in the Load Test Report. The default value is off.

  3. Click the Run button to start the load test.

  4. After the load test finishes, click the small arrow next to the Load Test button, and switch the option to View Report.

  5. Click the View Report button to see the Load Test Report.

Check Load Test Case Data

  1. Sometimes when you click the Load Test button on the right of the case name, you might see some warnings on the page. If you see the screenshot below, it means the recorded network information is incorrect. You need to use the IDA plug-in to replay the test case again.

  2. If you see the error below, it means your recorded load test data is out of sync. You also need to use the IDA plug-in to replay the test case again.

Note: The Load Test feature currently has the following limitations:

  • Frequently used test commands in the BPM category are supported.
  • Most test commands in the UI category are supported.
  • Assertion and Utility commands are not supported yet.

Categories:

Updated: