Performance test implementation specification Guide

1. Purpose

In order to implement the performance test , Make the plan management of performance test 、 Script management 、 Target management and report management have better readability 、 Readability , Enhance maintainability and reusability , At the same time, it is convenient to manage the summary and aggregation of data , Reduce the difficulty of users , This specification is specially prepared .

1. Scope of application

This guide is applicable to the performance test projects carried out .

1. Target audience

Test Manager 、 Performance tester 、 Performance test related personnel .

1. Performance test flow

1. Performance testing The code of practice

Combined with the requirements of current performance test implementation , For script management during performance test implementation , Plan management , The goal is （ scene ） management , Report management , Problem management should be standardized .

1. 1. Plan specification

Include plan name 、 Planning cycle 、 Plan version and plan test requirements .

Describe the intended scope of testing activities （ Which modules are tested ）、 Test resources （ software and hardware ） And schedule , Confirmed the test item 、 Tested features 、 Test task 、 Personnel arrangement and risk of any accidental events .

1. 1. 1. Script Naming specification

Scene number _ Function name

example ：S01_xx Sign in

Mixed scenes

example ：S01-88_XX scene  

1. 1. 1. The goal is （ scene ） Management specification

One target corresponds to one pressure measurement scene , Scene number _ Scene name or interface name

example ：S01_ Vehicle - Query vehicle configuration

1. 1. 1. The goal is （ Traffic configuration ） Management specification

Incremental time 0s,

Duration ： Index pressure measurement 600s, Stability pressure test 3-10 Hours

1. 1. 1. Label specifications

Add different tags for management , Easy to view and read . The specific requirements are as follows ：

Labels that must be marked ：

1. Plan type label ： Regular iteration 、 Mobile pressure measurement 、 Choose one of three new projects ;
2. The script type ： Single interface 、 Process class 、 Multithreading group mixing one of three
3. Test environment ： Simulation environment 、 Test environment 、 Production environment
4. Pressure test record ： Index archiving , Load archiving , Stable archiving
   1. Problem management specification

The test problem specification is mainly divided from the problem phenomenon and the technical dimension involved , As follows ：

A、 Problem phenomenon ：TPS Substandard , Slow response time 、 database CPU Super index 、 Memory leak 、 Application downtime 、 Uneven load 、 application CPU Exceeding or too low 、 The success rate of the transaction is lower than the index

B、 Technology dimension ： operating system -Linux, operating system -windows,Weblogic,Websphere,MQ,kafka,IIS,Tuxedo,SQLServer,Informix,Oracle,Sybase,redis,nginx,JVM etc.