close
The Wayback Machine - https://web.archive.org/web/20240818212524/https://www.geeksforgeeks.org/volume-testing/
Open In App

Volume Testing

Last Updated : 24 Apr, 2024
Comments
Improve
Suggest changes
Like Article
Like
Save
Share
Report
News Follow

Volume Testing is a type of software testing which is carried out to test a software application with a certain amount of data. The amount used in volume testing could be a database size or it could also be the size of an interface file that is the subject of volume testing. 

While testing the application with a specific database size, database is extended to that size and after that the performance of the application is tested. When an application needs interaction with an interface file this could be either reading or writing the file or same from the file. A sample file of the size required is created and then functionality of the application is tested with that file in order to test the performance. 

In volume testing a huge volume of data is acted upon the software. It is basically performed to analyze the performance of the system by increasing the volume of data in the database. Volume testing is performed to study the impact on response time and behavior of the system when the volume of data is increased in the database. 

Volume Testing is also known as Flood Testing. 

Characteristics of Volume Testing

Following are the characteristics of the Volume Testing:

  • Performance of the software decline as passing of the time as there is huge amount of data overtime.
  • Basically the test data is created by test data generator.
  • Only small amount of data is tested during development phase.
  • The test data need to be logically correct.
  • The test data is used to assess the performance of the system.

Objectives of Volume Testing

The objectives of volume testing is:

  • To recognize the problems that may be created with large amount of data.
  • To check The system’s performance by increasing the volume of data in the database.
  • To find the point at which the stability of the system reduces.
  • To identify the capacity of the system or application.

Volume Testing Attributes

Following are the important attributes that are checked during the volume testing:

  • System’s Response Time: During the volume testing, the response time of the system or the application is tested. It is also tested whether the system responses within the finite time or not. If the response time is large then the system is redesigned.
  • Data Loss: During the volume testing, it is also tested that there is no data loss. If there is data loss some key information might be missing.
  • Data Storage: During the volume testing, it is also tested that the data is stored correctly or not. If the data is not stored correctly then it is restored accordingly in proper place.
  • Data Overwriting: In volume testing, it is tested that whether the data is overwritten without giving prior information to the developer. If it so then developer is notified.

Volume Testing is a type of Performance Testing. 

performance-testing

Performance Testing

Advantages of Volume Testing

  • Volume testing is helpful in saving maintenance cost that will be spent on application maintenance.
  • Volume testing is also helpful in a rapid start for scalability plans.
  • Volume testing also helps in early identification of bottlenecks.
  • Volume testing ensures that the system is capable of real world usage.

Disadvantages of Volume Testing

  • More number of skilled resources are needed to carry out this testing.
  • It is sometimes difficult to prepare test cases with respect to the number of volume of data to be tested.
  • It is a time consuming technique since it requires lot of time to decide the number of volume of data and test scenarios.
  • It is a bit costly as compared to another testing technique.
  • It is not possible to have the exact break down of memory used in the real world application.
  • Testing Microservices Architecture: Modification of Volume Testing to assess scalability in applications with microservices and their interconnections.
  • Testing the Performance of Edge Computing: Volume testing should be expanded to guarantee top performance in edge computing settings.
  • Practices for Shift-Left Testing: Volume testing is incorporated early in the software development life cycle as a component of “Shift-Left” testing methodologies.
  • Testing Containerized Applications: Volume testing methodologies have been modified to evaluate scalability in containerized settings such as Kubernetes.
  • IoT Performance Testing of Devices: Utilizing specialized Volume Testing to address scalability issues specific to IoT ecosystems.

Conclusion

A crucial part of software testing is volume testing, which evaluates a system’s performance at different data volume levels. An extensive volume testing approach helps software applications be more dependable, effective and scalable overall, allowing businesses to provide solid solutions that satisfy customer and corporate needs.


Previous Article
Next Article

Similar Reads

Difference between Stress Testing and Volume Testing
Stress Testing: Stress testing is a type of software testing that is performed to test the stability and reliability of the system under extremely heavy conditions. It also tests the robustness of the system. Volume Testing: Volume Testing is a type of software testing that is performed to test the performance or behavior of the system or applicati
2 min read
Difference between Volume Testing and Load Testing
Volume Testing: Volume Testing is a type of software testing that is performed to test the performance or behavior of the system or application under the huge amount of data. Volume testing is also called flood testing and it is a type of performance testing. Load Testing: Load Testing is a type of software testing that is performed to test the per
2 min read
Unit Testing, Integration Testing, Priority Testing using TestNG in Java
TestNG is an automated testing framework. In this tutorial, let us explore more about how it can be used in a software lifecycle. Unit Testing Instead of testing the whole program, testing the code at the class level, method level, etc., is called Unit Testing The code has to be split into separate classes and methods so that testing can be carried
6 min read
Split Testing or Bucket Testing or A/B Testing
Bucket testing, also known as A/B testing or Split testing, is a method of comparing two versions of a web page to see which one performs better. The goal of split testing is to improve the conversion rate of a website by testing different versions of the page and seeing which one produces the most desired outcome. There are a few different ways to
15+ min read
Selenium Testing vs QTP Testing vs Cucumber Testing
Automation testing will ensure you great results because it's beneficial to increased test coverage. Manual testing used to cover only few test cases at one time as compared to manual testing cover more than that. During automated test cases it's not all test cases will perform under the tester. Automation testing is the best option out of there. S
6 min read
Difference between End-to-end Testing and Unit Testing
1. End-to-end Testing: End-to-end testing is the type of software testing used to test entire software from starting to the end along with its integration with the external interfaces. The main purpose of end-to-end testing is to identify the system dependencies and to make sure that the data integrity and communication with other systems, interfac
5 min read
Software Testing - Testing Retail Point of Sale(POS) Systems with Test Cases Example
POS testing refers to testing the POS application to create a successful working POS application for market use. A Point of Sale (POS) system is an automated computer used for transactions that help retail businesses, hotels, and restaurants to carry out transactions easily. What is Retail Point of Sale (POS) Testing?POS is a complex system with a
14 min read
Difference between Frontend Testing and Backend Testing
Front End Testing: Front End Testing is a type of testing that tests the presentation layer of a 3 tier architecture in a web application. Basically, front-end testing is performed on the user interface (UI) which is also known as the presentation layer in 3-tier architecture. Back End Testing: Back-end testing is a type of testing that tests the a
2 min read
Graphical User Interface Testing (GUI) Testing
Graphical User Interface Testing (GUI) Testing is the process for ensuring proper functionality of the graphical user interface (GUI) for a specific application.GUI testing generally evaluates a design of elements such as layout, colors and also fonts, font sizes, labels, text boxes, text formatting, captions, buttons, lists, icons, links, and cont
2 min read
Differences between White Box Testing and Gray Box Testing
White Box Testing: White Box Testing is a type of Software Testing in which the internal structure, design and implementation of the software application that is being tested is fully known to the tester. Gray Box Testing: Gray Box Testing is a software testing technique which is a combination of Black Box Testing technique and White Box Testing te
2 min read
Difference between Black Box Testing and Gray Box Testing
Black Box Testing: Black Box Testing is a Software Testing technique in which the tester doesn't know the internal structure, design and implementation of the software application that is being tested. Gray Box Testing: Gray Box Testing is a software testing technique which is a combination of Black Box Testing technique and White Box Testing techn
4 min read
Difference between Unit Testing and Integration Testing
Unit Testing: Unit Testing is a type of software testing where individual software components are tested. Unit Testing of the software product is carried out during the development of an application. An individual component may be either an individual function or a procedure. Unit Testing is typically performed by the developer. It is a testing met
2 min read
Difference between System Testing and Acceptance Testing
System Testing: System Testing is done to check whether the software or product meets the specified requirements or not. It is done by both testers and developers. It contains the Testings: System testing, Integration Testing. It is done through more positive and negative test cases. Acceptance Testing: Acceptance Testing is done after the system t
2 min read
Difference between Performance Testing and Load Testing
Performance Testing: Performance Testing is a type of software testing that is carried out to determine system performance in terms of sensitivity, reactivity, and stability under a particular workload. Load Testing: Load Testing is a type of software testing that determines the performance of a system, software product, or software application und
2 min read
Difference between Unit Testing and Sandwich Testing
Unit Testing: Unit Testing is the type of Software Testing level in which each individual components of a software are tested. Unit Testing is generally performed by developer. Unit Testing can't be used for those systems which have a lot of interdependence between different modules. It does not allow for parallel testing. Sandwich Testing: Sandwic
3 min read
PEN Testing in Software Testing
Pen testing, a series of activities taken out in order to identify the various potential vulnerabilities present in the system which any attack can use to exploit the organization. It enables the organization to modify its security strategies and plans after knowing the currently present vulnerabilities and improper system configurations. This pape
3 min read
Difference between Active Testing and Passive Testing
Active Testing: Active Testing is a type of software testing in which a tester interacts with a software as an end user. Tester assumes that he/she himself/herself is the user of the software and gives the different combinations of the input in order to validate the actual behavior of the software. Passive Testing: Passive testing is a type of soft
2 min read
Severity in Testing vs Priority in Testing
In software testing, a bug is the most critical entity. The most important attributes that can be assigned to a bug are priority and severity. They help teams to efficiently fix bugs and go through the release scheduling processes without letting any critical issues fall through the gaps. The article focuses on discussing the difference between Sev
6 min read
Difference between System Testing and End-to-end Testing
Introduction : System Testing and End-to-end Testing are two different types of software testing that are used to ensure the quality and functionality of a software system. System Testing is a type of testing that is performed on the complete system or software application to evaluate its behavior and performance. It is generally conducted after th
4 min read
Difference between System Testing and Integration Testing
Introduction : System testing and integration testing are two critical types of software testing that are used to ensure the quality and reliability of software products. Integration testing is a type of testing that focuses on verifying the interfaces and interactions between software components or modules. It is conducted after unit testing and e
4 min read
Difference between Scrum Testing and V-Model Testing
Scrum Testing: Scrum testing is a type of software testing that is used for testing the software in Agile Software Development Model. It is basically a framework used in agile software development process. Scrum testing is used to test the complicated software. Along with all these it also checks the quality, performance and the usability of the so
2 min read
Difference between Positive Testing and Negative Testing
Positive Testing: Positive testing is a type of software testing that is performed by assuming everything will be as expected. It is performed with the assumption that only valid and relevant things will occur. data set and all other functionalities will be as expected. Negative Testing: Negative testing is a type of software testing that is perfor
2 min read
Difference between Cucumber Testing and Selenium Testing
Cucumber Testing: Cucumber testing is a software testing which uses the tool that supports Behavior Driven Development (BDD). It offers a way to write tests that anybody can understand regardless of their technical knowledge. Selenium Testing: Selenium testing is a software testing that uses a tool that supports Functional and Performance (Selenium
2 min read
Difference between Database Testing and Data warehouse Testing
Database Testing: Database testing is the testing of security, performance and various other aspects of the database. It also includes various actions taken for testing of data. IT is basically performed on the small data size that is stored in the database system. Example: Testing of data of a college's students results. Data warehouse Testing: Da
2 min read
Difference between Pilot Testing and Alpha Testing
Pilot Testing: Pilot testing is the type of software testing where a group of users uses the software in totality before the final launch or deployment of the software. This testing verifies a component of the system or the entire system under a real time operating condition. The purpose of the pilot Testing is to evaluate the feasibility, time, co
2 min read
Difference between Scrum Testing and Waterfall Testing
1. Scrum Testing : Scrum testing is a type of software testing that is the part of agile testing. It is basically a framework used in agile software development process. Scrum testing is used to design the complicated software. It also checks the quality, performance and the usability of the software. Basically, it focuses on the development and ma
3 min read
Load Testing Basics, Tools & Practices in Software Testing
Introduction: Load testing is a type of performance testing that simulates a real-world load on a system or application to see how it performs under stress. The goal of load testing is to identify bottlenecks and identify the maximum number of users or transactions the system can handle. Some popular tools for load testing include Apache JMeter, Lo
6 min read
Difference between Smoke Testing and Regression Testing
Prerequisite - Software Testing 1. Smoke Testing : Smoke Test refers to an initial testing which is performed on newly developed software build . By this kind of software testing it is clear that the core functionalities of software product is working perfectly without any issues. If any case the software fails to pass the smoke testing then it is
3 min read
Basis Path Testing in Software Testing
Prerequisite - Path Testing Basis Path Testing is a white-box testing technique based on the control structure of a program or a module. Using this structure, a control flow graph is prepared and the various possible paths present in the graph are executed as a part of testing. Therefore, by definition, Basis path testing is a technique of selectin
5 min read
Difference between Sanity Testing and Regression Testing
Prerequisite - Software Testing 1. Sanity Testing: Sanity Testing refers to analyzing/testing the software after modification. It is a part of Regression Testing, where Regression Testing focuses on a wide variety of areas of the application, there Sanity Testing focuses only on certain functionalities. It examines the product quality and its readi
2 min read
three90RightbarBannerImg