Check List for performance testing (continuously updating)

A document prepared last year has recently been used for performance tests. I have provided a reference and shared it with you. Pai_^

If you think of more items, you can leave a message for discussion.

1. Have developers submitted a test application?

2. Are the test objects specified?

3. Is the test Scope clear?

4. Is the scope of this test not to be tested clear?

5. Are the test targets clear?

6. When will performance testing begin?

7. When will a performance test be terminated?

8. How many rounds of performance testing are required?

9. What is the required test environment? Is the configuration in place complete? (Including hardware, software, and network)

10. What test tools are required? Is it in place and can be used properly?

11. Is the version of the tested system clear? Published? Where can I get it? Is the deployment successful?

12. Have the functions of the tested system been correctly implemented?

13. Is the stress point clear? Is the calculation method of response time clear?

14. What documents are referenced in this test?

15. Has the scenario been designed and recorded in the scenario management document?

16. Are there clear test intentions, preconditions, and detailed settings for each scenario?

17. Has the script been recorded and debugged?

18. Have you made it clear where parameterization is required?

19. Have the values of various parameters been clarified?

20. Have necessary data been prepared for the parameterized part?

21. Have you prepared the corresponding historical data volume?

22. Have the corresponding data recovery methods been prepared? (For example, prepare an SQL statement to restore the data environment)

23. Has the multi-vu or multiple iterations been debugged in the controller?

24. Is the result path set correctly in the controller?

25. Check whether the script selection is correct in controller?

26. Check whether the VU quantity settings are correct in the controller?

27. Check whether the set point is disabled/enabled in the controller?

28. Check whether the VU loading policy is set correctly in the controller?

29. Check whether the number of iterations is set correctly in the controller?

30. Check whether the iteration Interval Settings are correct in the controller?

31. Check whether logs are disabled/enabled in the controller?

32. Check whether think_time is played back in the controller?

33. In the controller, check whether Resource Monitor is added to the Unix server and the load generator machine, and confirm that the performance data can be received?

34. In the controller, check whether resource monitors are added for other necessary resources and confirm that performance data (such as Oracle and WebSphere) can be received )?

35. Check whether the load generator machine can be connected in the controller?

36. Check whether the new "scenario execution status" is added to the scenario management document and the data before running is recorded?

37. Before executing the scenario in the controller, check whether vmstat and top are run on the Linux client to monitor the Linux server resource consumption during execution?

38. Do I check the data consistency in the system immediately after the execution scenario is completed in the controller, and fill in the running status in "scenario execution status?

39. After the scenario is completed, will the vmstat and top data be copied to notepad and saved to the corresponding result directory?

40. After the testing of the entire system is completed, have you analyzed the performance chart and submitted the test report?