Modern web applications are built using heavy javascript files. Many applications are providing application development online. Many applications are integrated with other systems. These are all forcing us to do a Performance test.
We need to define application performance first. You may think that using the following parameters we can define.
How fast servers are responding?
What is the response time of a request?
How the system is handling large set(1000 or 2000) of users?
Sometimes we need to consider all above parameters or any one. It depends on application
Remember the following key points before planning a Performance test.
Know your users:
You should know who is using your application, what type of users using your application, and finally how they use your application. You can get this information from production system logs, monitoring tools, sales and support team.
Test Data:
Test data should be close to production data. We should provide realistic data. We should not use non representative data, as it may not be easy to validate. We should not start with very large data, it should be equivalent to the production system. Test data should be increased depending on the understanding of the growth of data in the application.
Compare Test Environment & Production Environment:
We should replicate the test environment with the production environment. We should not execute performance test on a small machine and calculate the requirements. This never works.
We should use same machines, same database, same load balancers.. etc
We need to define application performance first. You may think that using the following parameters we can define.
How fast servers are responding?
What is the response time of a request?
How the system is handling large set(1000 or 2000) of users?
Sometimes we need to consider all above parameters or any one. It depends on application
Remember the following key points before planning a Performance test.
Know your users:
You should know who is using your application, what type of users using your application, and finally how they use your application. You can get this information from production system logs, monitoring tools, sales and support team.
Test Data:
Test data should be close to production data. We should provide realistic data. We should not use non representative data, as it may not be easy to validate. We should not start with very large data, it should be equivalent to the production system. Test data should be increased depending on the understanding of the growth of data in the application.
Compare Test Environment & Production Environment:
We should replicate the test environment with the production environment. We should not execute performance test on a small machine and calculate the requirements. This never works.
We should use same machines, same database, same load balancers.. etc
No comments:
Post a Comment