by Nataliia Vasylyna | July 27, 2015 8:14 am
Sometimes, the software creators have limitations in budget and time for the product release on the market, but, nevertheless, they are aware that the system should always be tested for compliance with quality requirements otherwise it can lead to large losses.
For such situations, when to perform a full range of software testing services is impossible because of some specific circumstances, a minimum package consisting of smoke testing and regression testing is usually offered.
Smoke testing is a bit like the functional testing[1] because of the uniformity of their targets. This is a short cycle of tests, which is performed to confirm that after the build of code (new or updated) the software runs properly and performs basic functions.
Regression testing[2] is aimed at verification changes after detection and fixing bugs in the application or the environment to ensure that pre-existing functionality works as before and has no unexpected adverse effects.
Thus, any software should be tested before the release, and even if the resources are rather limited, the customer can always use a set consisting of smoke testing and regression testing to ensure that the basic functions of the system were tested and bugs were corrected.
Source URL: https://blog.qatestlab.com/2015/07/27/regression-smoke-testing/
Copyright ©2024 QATestLab Blog unless otherwise noted.