load testing is the process of putting demand on a system or device and measuring its response. load testing is performed to determine a systemâs behavior under both normal and anticipated peak load conditions. it helps to identify the maximum operating capacity of an application as well as any bottlenecks and determine which element is causing degradation. when the load placed on the system is raised beyond normal usage patterns, in order to test the system's response at unusually high or peak loads, it is known as stress testing. the load is usually so great that error conditions are the expected result, although no clear boundary exists when an activity ceases to be a load test and becomes a stress test. there is little agreement on what the specific goals of load testing are. the term is often used synonymously with concurrency testing, software performance testing, reliability testing, and volume testing. load testing is usually a type of non-functional testing although it can be used as a functional test to validate suitability for use. ==software load testing==   the term load testing is used in different ways in the professional software testing community. load testing generally refers to the practice of modeling the expected usage of a software program by simulating multiple users accessing the program concurrently. as such, this testing is most relevant for multi-user systems; often one built using a client/server model, such as web servers. however, other types of software systems can also be load tested. for example, a word processor or graphics editor can be forced to read an extremely large document; or a financial package can be forced to generate a report based on several years' worth of data. the most accurate load testing simulates actual use, as opposed to testing using theoretical or analytical modeling. load testing lets you measure your website's qos performance based on actual customer behavior. nearly all the load testing tools and frame-works follow the classical load testing paradigm: when customers visit your web site, a script recorder records the communication and then creates related interaction scripts. a load generator tries to replay the recorded scripts, which could possibly be modified with different test parameters before replay. in the replay procedure, both the hardware and software statistics will be monitored and collected by the conductor, these statistics include the cpu, memory, disk io of the physical servers and the response time, throughput of the system unde
Load_testing_tools Quality_assurance Software_testing Tests