![[Level:23]](http://www.vietnamesetestingboard.org/zbxe/modules/point/icons/default/23.gif "Point:16150point (19%), Level:23/30"){kind=icon}
mathi.7664
Volume Testing
The purpose of volume testing is to determine system performance with increasing volumes of data in the database.
Here we are interested in the same indexes as performance testing, ie basically - running times, depending on the number of users, but in this case we are testing for large volumes of data.
In my practice is the case when the reporting system works great for Scope PRA data for half a year, but much worse is already working on even the annual data, and very bad working on data for 2 years.
The earliest candidates for volumetric testing, these are places where large volumes of data are selected from a database or perform a complex sql queries for data retrieval. I want to say that if the first place more or less obvious (where a lot of data is displayed, there are a lot of data and is selected from the database), the second - is not always obvious (you can see a couple of lines, but in order for these couple of lines to show the programmer had to dig floor base). Having little experience in programming and databases, and exact same integral for the tester intuition can try to find yourself in such a system bottlenecks, but nevertheless there is better to seek assistance from programmers who know the system and all its trouble spots inside.
That is, for load testing is necessary:
- identify places where large volumes of selected data from DB
- identify places where run complex sql queries
- Pour into a database for many, many data
- to test the performance
- if necessary - to perform stress testing
Written by
Mathi,
Testing executive
