CN104391789A - Web application stress testing method - Google Patents
Web application stress testing method Download PDFInfo
- Publication number
- CN104391789A CN104391789A CN201410652606.3A CN201410652606A CN104391789A CN 104391789 A CN104391789 A CN 104391789A CN 201410652606 A CN201410652606 A CN 201410652606A CN 104391789 A CN104391789 A CN 104391789A
- Authority
- CN
- China
- Prior art keywords
- test
- pressure test
- web application
- performance index
- described step
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention relates to the field of Web system performance testing technology, in particular to a Web application stress testing method. The method specifically includes the following steps: Step1: requirement analysis; Step 2: determination of a testing objective; Step 3: making of a stress testing plane; Step 4: system analysis; Step 5: compilation of a testing case; Step 6: setting of testing data; Step 7: stress testing; Step 8: result analysis; Step 9: optimization and adjustment of settings; Step 10: submission of a testing report. Through the steps, the Web application stress testing method enhances the performance and stability of Web applications, and can be used for testing the stress of Web applications.
Description
Technical field
The present invention relates to Web system technical field of performance test, the method for particularly web application pressure test.
Background technology
Web application is the key determining web site performance, and testing it is the core that website is tested.The object of pressure test is the performance of test macro under various load (the overall treatment amount produced by concurrent user) and stability.
In order to ensure that the pressure test of web application can obtain desirable test effect, pressure test also should follow the General Requirements of software test in soft project.Pressure test should be paid attention to accordingly.
Summary of the invention
The technical matters that the present invention solves is a kind of method providing web application pressure test; Solve the performance of web application and the problem of stability.
The technical scheme that the present invention solves the problems of the technologies described above is:
Comprise following step:
Step 1: demand analysis;
Step 2: determine test target;
Step 3: formulate pressure test plan;
Step 4: analytic system;
Step 5: write test cases;
Step 6: test data is set;
Step 7: carry out pressure test;
Step 8: analysis result;
Step 9: optimize and revise setting;
Step 10: submit test report to.
In described step 2, the object of definition test, and clear explanation is provided to each tested object, and the target that definition test terminates; Definition criterion and strategy, to judge when terminate test phase.
In described step 3, the content of test plan mainly comprises: definition test resource, formulation testing progress table, selection testing tool etc.
In described step 4, analytic system comprises: the first, and certainty annuity is to each distribution of resource and service condition, and it will help us to determine the bottleneck of possible system performance; The second, determine the distribution of user's business, determine pressure test for point.
In described step 5, test cases should load that is virtually reality like reality as far as possible, does not omit important test path; In test cases, when should indicate test scene, test event, test, require the performance index etc. of record; Described performance index are mainly divided into client performance index and the large class of server end performance index two.
In described step 8, analytic target has: the response time (having how many users simultaneously to run) of the time that (1) test uses and tested affairs; (2) the process number of pressure test participation, successful number, failed number; (3) pressure test participates in the reason of process failure; (4) variation diagram that increases with user of the response time of affairs; (5) resource restriction.
Beneficial effect of the present invention: the method for web application pressure test provided by the invention; Efficiently solve the performance of web application and the problem of stability.
Accompanying drawing explanation
Below in conjunction with accompanying drawing, the present invention is further described:
Fig. 1 is method flow diagram of the present invention.
Embodiment
As shown in Figure 1, the method for web application pressure test of the present invention, specifically comprises following step:
Step 1: carried out demand analysis before this; Also different with emphasis to the intensity of different its pressure tests of system.One will process the load of the e-commerce site of a large number of users for medium-sized and small enterprises in-house network and one and power load distributing is visibly different.The former maximal workload and power load distributing are expected, and concerning enterprises and institutions' in-house network, resetting after temporary close system is also acceptable.The Course-Selecting System of such as colleges and universities only requires that in several days that carry out curricula-variable system can bear large load, and its load is almost nil At All Other Times; And cannot expect there is how many client meeting access site simultaneously for the latter, also cannot predict the time that peak load occurs.Therefore must carry out demand analysis before pressure test, it is the basis of writing good test cases.
Step 2: determine test target; Determining that, in pressure test target, we will define the object of test, and clear explanation is being provided to each tested object, also will define the target that test terminates.For controlling validity and the performance level of test, criterion and strategy must be defined, to judge when terminate test phase.Criterion must be objective, quantifiable, and can not be experience or sensation.Here is some pressure test targets: (1) measures the response time of terminal user affairs, and it may increase with the increase of user, but will define one and can accept the time.(2) define main frame allocation optimum, we can play best performance with minimum price.In pressure test target deterministic process, user, designer etc. be invited to evaluate it.
Step 3: formulate pressure test plan; The content of test plan mainly comprises: definition test resource, formulation testing progress table, selection testing tool etc.The fundamental purpose formulating test plan is guarantee pressure test being had regulations to abide by and obtains human and material resources aspect.It is to be noted formulate testing progress table time mutually should coordinate with development progress.When an exploitation web application, system is divided into some independent subsystems by the difference according to function.Good method completes along with subsystem the pressure test first carrying out subsystem, certainly, finally also must carry out the comprehensive pressure test of whole system.
Step 4: analytic system; Analytic system has two main tasks: the first, and system of getting clear is to each distribution of resource and service condition, and it will help us to determine the bottleneck of possible system performance; The second, get the distribution of user's business clear, determine pressure test for point.We define the operation task that affairs are used to represent that user requires server to complete continuously.Because most systems is all network system, and network is also usually the main cause reducing the response time, so we carry out the resource of analytic system by resource schematic diagram.In order to illustrate in greater detail the performance of resource, we require to tabulate the attribute of each resource in resource schematic diagram.Such as, for router, the system that it runs is described, its network throughput, response time etc.; For telecommunication media, its performance, capacity etc. are described; For main frame, its cpu performance, memory size, I/O peripheral hardware performance, the operating system of operation, Database Systems, application software system are described, also have the CONFIG.SYS etc. running application software system.
Step 5: write test cases; Tester will carry out actual test job according to test cases, the writing of test cases should accomplish objective comprehensively, give prominence to the key points, namely require that the test cases write should load that is virtually reality like reality as far as possible, do not omit important test path.In test cases, when should indicate test scene, test event, test, require the performance index etc. of record.Concerning web application, these performance index are similar, and performance index are mainly divided into client performance index and the large class of server end performance index two.
Step 6: test data is set; Data-driven version taked by pressure test script.In order to allow all processes perform smoothly, parametrization must be carried out to test data.The one group of test data simultaneously run needs to be unique each other sometimes, and sometimes needing sequentially, sometimes needs random, sometimes need data in an interval, sometimes needs to extract data from certain table of database.Data after parametrization and former data type should be consistent.The dirigibility arranging test data is very large, also very large to the Influence on test result of test, should according to circumstances, make concrete analyses of concrete problems.
Step 7: carry out pressure test; General not advocating carries out pressure test in development environment, if can not build test environment in addition due to funds reason, then the configuration of runtime server in the future should be identical with the configuration of staging server or better.If simulate hundreds of concurrent user, multiple stage client computer just should be adopted to test simultaneously, because the thread that a machine runs will cause hydraulic performance decline too much, thus make client computer can not process the response returned from server in time, cause test error.When performing pressure test, even same browse path also should repeatedly be tested, the interval time repeatedly between test is random, could obtain more objective test result like this.
Step 8: analysis result; After pressure test end of run, the data summarization of all records is recorded in file.Must analyze the result of test, just can obtain conclusion.Some figures can be used compare, observation test result.The content that analytic target records when being also test run, here is the analytic target of pressure test: the response time (having how many users simultaneously to run) of the time that (1) test uses and tested affairs; (2) the process number of pressure test participation, successful number, failed number; (3) pressure test participates in the reason of process failure; (4) variation diagram that increases with user of the response time of affairs; (5) resource restriction.
Step 9: optimize and revise setting; If test crash, must failure cause be analyzed, if system causes, designer's amendment should be returned to.Test result does not meet anticipated demand, need to system be optimized adjustment arrange, and then testing results, analysis, until can anticipated demand be met, or adjustment cannot improve result.Optimizing and revising setting and should cooperate and carry out with exploitation and system manager system.Performance issue interknits often, instead of incoherent mutually.System performance is lower, may be due to the problem optimized with arrange.By the performance optimized with can improve system when being provided with.
Step 10: submit test report to; When pressure testing results can meet anticipated demand, or optimize and adjustment cannot improve result.Finally submit test report to.Will comprise test summary, test environment and test result in report, summary should simple declaration method of testing, strategy, scope, content; Test environment should comprise resource overhead, environment configurations etc.; Whether result test must comprise test and pass through or refusal, is described, makes evaluation to the performance of system to the conclusion of test.Test result will comprise result data.
Claims (10)
1. a method for web application pressure test, is characterized in that:
Comprise following step:
Step 1: demand analysis;
Step 2: determine test target;
Step 3: formulate pressure test plan;
Step 4: analytic system;
Step 5: write test cases;
Step 6: test data is set;
Step 7: carry out pressure test;
Step 8: analysis result;
Step 9: optimize and revise setting;
Step 10: submit test report to.
2. the method for web application pressure test according to claim 1, is characterized in that: in described step 2, the object of definition test, and provides clear explanation to each tested object, and the target that definition test terminates; Definition criterion and strategy, to judge when terminate test phase.
3. the method for web application pressure test according to claim 1, is characterized in that: in described step 3, and the content of test plan mainly comprises: definition test resource, formulation testing progress table, selection testing tool etc.
4. the method for web application pressure test according to claim 2, is characterized in that: in described step 3, and the content of test plan mainly comprises: definition test resource, formulation testing progress table, selection testing tool etc.
5. the method for the web application pressure test according to any one of Claims 1-4, it is characterized in that: in described step 4, analytic system comprises: the first, and certainty annuity is to each distribution of resource and service condition, and it will help us to determine the bottleneck of possible system performance; The second, determine the distribution of user's business, determine pressure test for point.
6. the method for the web application pressure test according to any one of Claims 1-4, is characterized in that: in described step 5, and test cases should load that is virtually reality like reality as far as possible, does not omit important test path; In test cases, when should indicate test scene, test event, test, require the performance index etc. of record; Described performance index are mainly divided into client performance index and the large class of server end performance index two.
7. the method for web application pressure test according to claim 5, is characterized in that: in described step 5, and test cases should load that is virtually reality like reality as far as possible, does not omit important test path; In test cases, when should indicate test scene, test event, test, require the performance index etc. of record; Described performance index are mainly divided into client performance index and the large class of server end performance index two.
8. the method for the web application pressure test according to any one of Claims 1-4, it is characterized in that: in described step 8, analytic target has: the response time (having how many users simultaneously to run) of the time that (1) test uses and tested affairs; (2) the process number of pressure test participation, successful number, failed number; (3) pressure test participates in the reason of process failure; (4) variation diagram that increases with user of the response time of affairs; (5) resource restriction.
9. the method for web application pressure test according to claim 5, it is characterized in that: in described step 8, analytic target has: the response time (having how many users simultaneously to run) of the time that (1) test uses and tested affairs; (2) the process number of pressure test participation, successful number, failed number; (3) pressure test participates in the reason of process failure; (4) variation diagram that increases with user of the response time of affairs; (5) resource restriction.
10. the method for web application pressure test according to claim 6, it is characterized in that: in described step 8, analytic target has: the response time (having how many users simultaneously to run) of the time that (1) test uses and tested affairs; (2) the process number of pressure test participation, successful number, failed number; (3) pressure test participates in the reason of process failure; (4) variation diagram that increases with user of the response time of affairs; (5) resource restriction.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410652606.3A CN104391789A (en) | 2014-11-17 | 2014-11-17 | Web application stress testing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410652606.3A CN104391789A (en) | 2014-11-17 | 2014-11-17 | Web application stress testing method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104391789A true CN104391789A (en) | 2015-03-04 |
Family
ID=52609697
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410652606.3A Pending CN104391789A (en) | 2014-11-17 | 2014-11-17 | Web application stress testing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104391789A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776337A (en) * | 2016-12-29 | 2017-05-31 | 北京金山安全软件有限公司 | Performance analysis method and device and electronic equipment |
| CN106855843A (en) * | 2015-12-09 | 2017-06-16 | 北京神州泰岳软件股份有限公司 | The method for analyzing performance and device of a kind of Web system |
| CN106878328A (en) * | 2017-03-22 | 2017-06-20 | 福建中金在线信息科技有限公司 | A kind of website testing method and device |
| CN106961478A (en) * | 2017-03-27 | 2017-07-18 | 中国农业银行股份有限公司 | A kind of message processing method and device |
| CN111209178A (en) * | 2020-01-13 | 2020-05-29 | 中信银行股份有限公司 | Full link bottleneck testing method and system |
| CN114003482A (en) * | 2020-07-28 | 2022-02-01 | 苏州沈苏自动化技术开发有限公司 | Method and system for testing pressure of coding-free software system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102567186A (en) * | 2010-12-08 | 2012-07-11 | 上海杉达学院 | Automated software testing method |
| CN103257917A (en) * | 2012-02-16 | 2013-08-21 | 广州博纳信息技术有限公司 | Management method for software evaluation system |
| EP2685383A1 (en) * | 2012-07-13 | 2014-01-15 | Synchronoss Technologies, Inc. | Method and apparatus for unassisted data collection, extraction and report generation and distribution |
-
2014
- 2014-11-17 CN CN201410652606.3A patent/CN104391789A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102567186A (en) * | 2010-12-08 | 2012-07-11 | 上海杉达学院 | Automated software testing method |
| CN103257917A (en) * | 2012-02-16 | 2013-08-21 | 广州博纳信息技术有限公司 | Management method for software evaluation system |
| EP2685383A1 (en) * | 2012-07-13 | 2014-01-15 | Synchronoss Technologies, Inc. | Method and apparatus for unassisted data collection, extraction and report generation and distribution |
Non-Patent Citations (1)
| Title |
|---|
| 王万平: ""十步完成 Web 应用程序压力测试"", 《中国计算机报》 * |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106855843A (en) * | 2015-12-09 | 2017-06-16 | 北京神州泰岳软件股份有限公司 | The method for analyzing performance and device of a kind of Web system |
| CN106855843B (en) * | 2015-12-09 | 2020-04-03 | 北京神州泰岳软件股份有限公司 | Performance analysis method and device of Web system |
| CN106776337A (en) * | 2016-12-29 | 2017-05-31 | 北京金山安全软件有限公司 | Performance analysis method and device and electronic equipment |
| CN106878328A (en) * | 2017-03-22 | 2017-06-20 | 福建中金在线信息科技有限公司 | A kind of website testing method and device |
| CN106961478A (en) * | 2017-03-27 | 2017-07-18 | 中国农业银行股份有限公司 | A kind of message processing method and device |
| CN111209178A (en) * | 2020-01-13 | 2020-05-29 | 中信银行股份有限公司 | Full link bottleneck testing method and system |
| CN114003482A (en) * | 2020-07-28 | 2022-02-01 | 苏州沈苏自动化技术开发有限公司 | Method and system for testing pressure of coding-free software system |
| CN114003482B (en) * | 2020-07-28 | 2024-02-13 | 沈苏科技(苏州)股份有限公司 | Coding-free software system pressure testing method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110309071B (en) | Test code generation method and module, and test method and system | |
| Bai et al. | Cloud testing tools | |
| CN104391789A (en) | Web application stress testing method | |
| Sahaf et al. | When to automate software testing? decision support based on system dynamics: an industrial case study | |
| EP2572294B1 (en) | System and method for sql performance assurance services | |
| US10496768B2 (en) | Simulating a production environment using distributed computing technologies | |
| Chen et al. | Towards understanding cloud performance tradeoffs using statistical workload analysis and replay | |
| CN104378252A (en) | Cloud testing service platform | |
| US20140201714A1 (en) | Evaluating performance maturity level of an application | |
| Garousi et al. | When to automate software testing? A decision‐support approach based on process simulation | |
| Liu | Research of performance test technology for big data applications | |
| Chen | We don’t know enough to make a big data benchmark suite-an academia-industry view | |
| Srikanth et al. | Regression testing in software as a service: An industrial case study | |
| US9823999B2 (en) | Program lifecycle testing | |
| Izquierdo et al. | An empirical study on the maturity of the eclipse modeling ecosystem | |
| CN111459814A (en) | Automatic test case generation method and device and electronic equipment | |
| CN102014163A (en) | Cloud storage test method and system based on transaction driving | |
| CN106843822B (en) | Execution code generation method and equipment | |
| US20160335171A1 (en) | Test automation modeling | |
| Fagerström et al. | Verdict machinery: On the need to automatically make sense of test results | |
| Cai et al. | Analysis for cloud testing of web application | |
| CN105607892A (en) | Concurrent execution method and system of multiple programs | |
| CN111782557B (en) | Method and system for testing web application permission | |
| Kamma et al. | Effect of task processes on programmer productivity in model-based testing | |
| CN104615513A (en) | Multilevel code standardization breakdown analyzing method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20150304 |
|
| WD01 | Invention patent application deemed withdrawn after publication |