Volume testing

<p>Volume testing belongs to the group of <a href="/facts/Non-functional_tests/jbz7IqoR">non-functional tests</a>, which are a group of tests often misunderstood and/or used interchangeably. Volume testing refers to <a href="/facts/Software_testing/VoXzG9Tb">testing</a> a <a href="/facts/Software_engineering/KX6cE9kz">software application</a> with a certain amount of <a href="/facts/Data/AUBFN97o">data</a> to assert the system performance with a certain amount of data in the <a href="/facts/Database/VYcpkevb">database</a>. Volume testing is regarded by some as a type of <a href="/facts/Load_testing/fHRPN97k">capacity testing</a>, and is often deemed necessary as other types of tests normally don't use large amounts of data, but rather typically use small amounts of data. It is the only type of test which checks the ability of a system to handle large pools of data. For example, the test can be used to stress the database to its maximum limit. While the amount can, in generic terms, be the database size, it could also be the size of an <a href="/facts/Interface_(computer_science)/zdfp8unT">interface</a> file that is the subject of volume testing. For example, if one wants to volume test an application with a specific database size, the database will be expanded to that size and the application's <a href="/facts/Performance/LoPW1hxp">performance</a> will then be tested on it. Another example could be when there is a requirement for the application to interact with an interface file (could be any file such as <a href="/facts/.dat/y6rI6UFS">.dat</a>, <a href="/facts/.xml/clNgUfWk">.xml</a>); this interaction could be reading and/or writing on to/from the file. A sample file of an intended size can then be created and used to test the application's functionality in order to test the performance.
</p>

Volume testing open-in-new

Volume testing