Difference Between load Testing and Stress Testing ( load testing Vs Stress Testing )
Priority vs Severity
High Severity – High Priority bug This is when major path through the application is broken, for example, on an eCommerce website, every customers get error message on the booking form and cannot place orders, or the product page throws a Error of page not found. High Severity – Low Priority bug This happens when the bug causes major problems, but it only happens in very rare conditions or situations, for example, customers who use very old browsers cannot continue with their purchase of a product. Because the number of customers with very old browsers is very old version, it is not a high priority to fix the issue. High Priority – Low Severity bug The logo or name of the company is not displayed on the website. It is important to fix the issue as soon as possible, although it may not create cause a System and other component. Low Priority – Low Severity bug The privacy policy page take a long time to load. Not many people view the privacy policy page and slow...
-> Testing the app with maximum number of user and input is defined as load testing. While testing the app with more than maximum number of user and input is defined as stress testing.
ReplyDelete->In Load testing we measure the system performance based on a volume of users. While in Stress testing we measure the breakpoint of a system.
-> While stress testing is testing the application for unexpected load. It includes
Example:
If an app is build for 500 users, then for load testing we check up to 500 users and for stress testing we check greater than 500.