"Veterans talk test" I want to let the performance test no longer "unattainable" _ Software Testing

Article Source: http://www.51testing.com/html/35/n-3724335.html

I from the zero-distance contact performance test to today, but also only a year of time, in this road through the rugged winding, the taste sensed, indescribable.　　Although I've been getting started to "give up", I've been thinking and looking for how to make performance testing no longer seem so unattainable. Performance testing is actually a category of testing, then the corresponding, it is a set of standard process, no matter is the requirements analysis, test plan development, test implementation, analysis of the results of several links.
Therefore, for the performance test process in several aspects, I put myself into the original small white, to think about what they most hope to get what kind of support and help, and then combine the thinking of product, think out the following such a can be copycat "performance test framework or guidance system."
1, what is.
Definition and interpretation of common basic concepts, test methods and standard processes in performance testing;
2, what to do.
The performance test needs analysis method, can use the checklist problem form to help the user to arrive the corresponding demand to use the performance test kind, is the pressure test, is the stability test, or the robustness test and so on;
3, how to do.
3.1 corresponding to the above 2nd step, the specific test types, each have a corresponding test method description, including the need to prepare what data, steps and how to select the corresponding script to modify or assemble;
3.2 A set of corresponding sample libraries, contains scripts (. usr), parameterized files (. dat), scenarios (. lrs), which, although not entirely generic or applied, can be applied at least in the performance tests of similar products, which are relatively independent, structurally clear packets of one. Easy to update and manage;
4, how.
The system generates a report after the performance test is complete. For the commonly used single analysis diagram and combinatorial analysis diagram, the sample diagram and my actual diagram are compared, and tell me these data graphs, which represent the performance of the indicators, the value of these indicators, and respectively represent the performance is good or bad;
5, how to do.
For common performance issues, ROM lists common solutions, such as whether you should check and optimize SQL, or whether you should modify the number of server-side Tomcat connections, and so on.
If you can have such a set of product performance testing framework, then I think the performance test this mountain for most test engineers, is not so "unattainable", right.
Guided job files, test plan templates, independent test data and test scripts, distributed test environments build scripts or manuals, test reports, and corresponding analysis templates to support a complete set of performance testing frameworks to quickly fall into the ground and adapt quickly to different projects, and allows the test engineer to complete the performance test task with minimal learning cost.
However, such a set of frameworks can not be built overnight, it must be in the performance test engineers have a very deep understanding of the theory, and through a number of projects in the actual combat, summed up and formed a set of methodological system, supplemented by relatively independent data and scripts, planning templates, analysis steps and templates and other related tools. Continuous grinding, optimization and improvement to form a set of either the entry-level white, or the ongoing veteran, can easily use it to ascend the peak of such a product.