Exp. Share | Performance Testing tutorial, step by step, complete guide (2)

3 min readNov 13, 2020


51Testing | Software Testing Service Provider |Friday, 13th Nov. 2020

51Testing-Performance Testing Tutorial

After completing the testing requirement research, we move to the next step.

2. Testing preparation

The testing preparation stage is an important part of performance testing. During this stage, it is necessary to complete the following steps: business model and testing model building, performance testing implementation plan design, performance testing case design, performance testing monitoring plan design, performance testing script, and testing data preparation. And carry out the admittance inspection after the preparation.

Focus on: testing model building, plan design, case design, data preparation, etc.

51Testing-Performance testing

Key points description

  • Testing model building

The performance test implementer is in charge of testing model building.

Based on requirements analysis, analyze the collected information from research, pay close attention to cross-systems transaction paths, transaction relation, data disposal and circulation, business volume, transaction ratio, typical transaction, and the processing capacity, specifically identify multiple business scenarios, choose a detailed business transaction set for each scenario, and build the corresponding testing model according to business volume.

The output of this stage is the various testing scenarios, and the typical transaction in the scenario, and their proportion in the scenario.

  • Testing plan design

Performance testing implementation plan design is a must-to-do in performance testing with an output of <Performance testing plan>.

You should describe the following parts in the plan: testing requirements, start-stop standard, testing model design, testing strategy, testing items, testing environments and tools, and output documents of each stage. You should also explain the testing schedule, expected risks, and aversion methods in the plan. The testing model includes testing scenarios as well as typical transactions and ratios.

  • Cases design

Cases design include case description, environment(hardware, software, application version, testing data), delay settlement, pressure scenario, implementation description, expected results, and monitoring points.

Cases design is an important part of performance testing, the output of case design is <Performance testing cases>.

  • Data preparation

Data preparation involves the preparation of basic data. The quantity and logical relationship of testing data are very strict. The basic test data is usually based on self-generated simulation data or online data after desensitization.

  • Testing script development

Testing descript development is where LR comes to matter.

A test script is a programmatic embodiment of business operations, and a script is generally a description of a business process. This stage is mainly for the recording (writing), modification, and debugging of the script, so as to ensure that the script of each test case can be executed correctly under the conditions of a single and a small number of iterations before the test is implemented. The general steps of test script development are as follows:

Complete script code generation through recording or writing. When the code is generated, transactions are inserted mainly according to the needs, as the unit of statistical transaction response time during the test process;

Set parameters according to the test requirements;

Set checkpoints to check whether the transaction is executed correctly according to the message content field, that is, the checkpoint is set at the application;

Determine whether to set up a consolidation point according to the test requirements.

— — —

If you are interested in the first part, please go to

Exp. Share | Performance Testing tutorial, step by step, complete guide (1)

The last part is coming soon, stay tuned!




51Testing provides professional software testing services certificated by ISO9001:2008, ISO27001, ISO20000, and CMMI4.