Performance Testing :: Module 3 :: Topic 5.6 :: Test Data Configurations ( Read)
This article is a part of the Self-paced Learning Series for the Course: Performance TestingPlease refer to the link for more details on the Course.
Introduction of Worksoft SaaS Feature/Concept :: Lesson 5 :: Topic 5.6
1. Preparing Data for Testing
With the above topic we have built our automation to run the performance test. Now, lets see how to prepare Test Data and preconditions to checked before runnning performance test.
Test Data that is being used in performance tests has lot of impact on how our the application is reacting. Lets see how, for example user is searching for product A and search results are 100 records and when searched for product B, the search results are 500+. Here, the same page of application responds differently as the number of search results are varying.
Once after getting ready with test data,
1. Please see if you can reuse the same test data for multiple performance tests. If the test data is not reusable, the performance test fails and there will be lost of minutes and time. To make sure that performance tests go smoothly, everytime the test data to be refreshed before running test.
2. By using certain test data, business scenarios in performance tests might create records or values in data base. In this case, by using the same test data, the same records might get created. we need to check if the duplicate records are accepted by database otr not. If not, regularly the records or data created should be cleaned up.
3. While refreshing test data, make sure to back up your test data by performance test name or/and data. If the results of the performance tests are varying, back up data will be used to cross check.
4. Atlast, if the business scenario is expecting to login, check to use multiple user or single user. In real time, there will be both the cases, login to application happens by using different accounts and also different users using same login.
Please consider all of the above points as checklist and use as a referebce before running the performance test. By this we can also reduce the failures of performance tests.
Test Data that is being used in performance tests has lot of impact on how our the application is reacting. Lets see how, for example user is searching for product A and search results are 100 records and when searched for product B, the search results are 500+. Here, the same page of application responds differently as the number of search results are varying.
Once after getting ready with test data,
1. Please see if you can reuse the same test data for multiple performance tests. If the test data is not reusable, the performance test fails and there will be lost of minutes and time. To make sure that performance tests go smoothly, everytime the test data to be refreshed before running test.
2. By using certain test data, business scenarios in performance tests might create records or values in data base. In this case, by using the same test data, the same records might get created. we need to check if the duplicate records are accepted by database otr not. If not, regularly the records or data created should be cleaned up.
3. While refreshing test data, make sure to back up your test data by performance test name or/and data. If the results of the performance tests are varying, back up data will be used to cross check.
4. Atlast, if the business scenario is expecting to login, check to use multiple user or single user. In real time, there will be both the cases, login to application happens by using different accounts and also different users using same login.
Please consider all of the above points as checklist and use as a referebce before running the performance test. By this we can also reduce the failures of performance tests.