Top 10 Performance Testing Mistakes

上一篇 / 下一篇  2011-06-18 17:07:06 / 个人分类:性能测试

1 Incorrect Load Levels

Fix: Improve and focus communications by conducting a one-on-one interview to determine expected “real world” load levels. If the application is already in production, obtain live usage data.

2 Performance Tester Identifying Key Business Processes

Fix: Conduct a one-on-one interview to identify key business processes: mission critical, heavy throughput, dynamic content, and any other business process that causes concern.

3 Too Many Business Processes

Fix: Concentrate on a few, perhaps 6-8, key business processes for performance testing – this is not a functional test.

4 Altering Load Test Objectives

Fix: Develop a complete custom plan with goal load levels, business process steps, transaction names, and acceptable response times. Analyze any missed objectives – stay consistent with the original goals unless there is a compelling reason for change.

5 Late Focus on Performance Testing

Fix: Engage the performance testing team as early as possible in the development life cycle to allow time between executions for a good analysis of the results from the performance tester. Detecting and correcting performance issues early reduces the repair cost.

6 Poor Transaction Naming Convention

Fix: For easier analysis, maintainability, future growth, and possible server consolidation, provide a clear naming convention.

7 Performance Tester Stands Alone

Fix: Let the experts do what they do best. Involve all members of the team: the DBA, Web Server Expert, Application Expert, Developer, etc. Executing a performance test is best done as a team.

8 Not Validating the Execution Transaction Levels

Fix: Validating transaction levels against the test plan after executing a full load test ensures the test presented the desired load to the application.

9 Server Experts Become Bouncy

Fix: If possible, don’t bounce the server between test executions. Bouncing the server prior to every test causes the need to rebuild the memory and cache. Memory leaks and other reliability and availability issues will be more easily identified if the server is left untouched.

10 Over-technical on Results Reporting

Fix: Performance testing creates mountains of data that are usually very interesting to technical experts. Ultimately, however, the owners of the application are looking for key performance indicators to make a sound business decision for their application go-live. Create a one-minute overview for managers that concisely conveys the critical data related to application performance.





Open Toolbar