Post Link : https://www.skptricks.com/2018/08/7-types-of-web-performance-tests.html
Software Performance testing is type of testing perform to determine the performance of system to major the measure, validate or verify quality attributes of the system like responsiveness, Speed, Scalability, Stability under variety of load conditions. The system is tested under a mixture of load conditions and check the time required responding by the system under varying workloads. Software performance testing involves the testing of application under test to ensure that application is working as expected under variety of load conditions. The goal of performance testing is not only find the bugs in the system but also eliminate the performance bottlenecks from the system.
7 Types of Web Performance Tests :
Performance Test: A performance test is any test that measures stability, performance, scalability and/or throughput of your web application(s).
Capacity Test: A capacity test is a test to determine how many users your application can handle before either performance or stability becomes unacceptable. By knowing the number of users your application can handle “successfully”, you will have better visibility into events that might push your site beyond its limitations. This is a way to avoid potential problems in the future.
Load Test: A load test consists of applying load to an application and measuring the results. The load may or may not be at the high end of application capacity. These tests can help determine normal performance metrics. By using iterative testing, you can determine whether new code has helped or hurt performance.
Stress Test: A stress test is a test that pushes an application beyond normal load conditions. When you push your application to the extreme, you will see which components fail first. Making these components more robust, or efficient, will help determine new thresholds.
Soak Test: A soak test is a long-running test that is used to determine application performance and/or stability over time. An application may work well for an hour or two, and then start to experience issues. These tests are especially useful when trying to track down memory leaks or corruption.
Component Test: Testing a discrete component of your application requires a component test. Examples might include a search function, a file upload, a chat feature, an email function, or a 3rd-party component like a shopping cart.
Smoke Test: A smoke test is a test run under very low load that merely shows that the application works as expected. The term originated in the electronics industry and refers to the application of power to an electronic component. If smoke is generated, the test fails and no further testing is necessary until the simplest test passes successfully. For example, there may be correlation issues with your scenario or script – if you can run a single user test successfully, the scenario is sound. It is a best practice to initate one of these “verification” runs before running larger tests to ensure that the test is valid.
Thank you for reading this article, and if you have any problem, have a another better useful solution about this article, please write message in the comment section.
Top comments (3)
within my team we don't consider smoke tests like performance test but as a non regression test for the happy path (placing orders)
That's like my place, too. Smoke isn't regarding performance but more of a functional happy path of checking if the main workflows work (can you get 4 pages in or does the build utterly break along the way?)
I agree :) smoke and component tests are not performance tests although you can do performance testing against a component