Software Testing Experts

Stress Testing is the testing to verify the response/output of the software beyond the breaking point of the system. In Stress Testing, Test team focus on robustness, availability and the error handling under the heavy load rather then correct behavior under normal circumstances. It is the type of non functional testing.

In Volume Testing, application is test with the huge amount of data as name applies. Volume Testing is the Non-Functional Testing. When tester test the volume Testing, we need to extend the size of the database to store the large amount of data.

A Soak Testing is a typical production load for continuous available period to check system behavior under production use.  Soak Test also called the Endurance Test. It is a non-function Testing.

Meaning of Load Testing is to provide constantly or steadily  load for a software to check that how software is responding in increasing load without significant performance degradation. Load Testing is put load over the system to check the response. We increase the limit until the threshold limit. In Load Testing we determine the system limit in normal load and peak load limit of the system. If we increase the load then peak to check system response this will called the Stress Testing .

Performance Testing is the testing in which Test Team determine how the system will perform in terms of responsiveness and when the system will be overloaded. In Performance Testing , we validate or verify the scalability, reliability and how the system uses the available resources. These all are the quality attribute of the system.

In the terms in programming context, build is the version of the program. Build is the executable code which is used for the Testing Purpose. Build is just the version for the testing team to test the software before release it to the customer.

Sanity Testing is perform when QA team received the build after fixes of minor bugs or some new functionality added. In Sanity Testing, QA team check that the bugs that generated in last build should be fix and due to those bug fixes there should be no new bugs generated. So in Sanity Testing first QA team check the regression testing and after regression testing QA team verify the previous bugs.