#features of testing

[fintest]

Sanity Testing

What is Sanity testing or Sanity checks? In general, this technique is a subtype of regression testing, that is included for basic tests. We apply this technique of software testing right after receiving a build with minor changes. The objective is to confirm that the given system still functions fine and new modifications did not bring about any issues. In case some bugs occur, the build will not be ready for the further testing. Sanity tests are rather narrow, because it usually deals only with one or just a few areas of functionality. The specific nature of this type of functional testing is that this testing is usually unscripted, or in other words, it is usually not documented nor structured. As for the objectives of sanity testing, testers use it with the purpose of checking the readiness of the system and is done before commencing with far more rigorous testing. Read the full article

[fintest]

Smoke testing

Functional testing is a broad class of tests that can be categorized into different types. Among them is Smoke testing. Simply put, it is a type of software testing that is typically performed during the initial stages of developing a system. The main objective of Smoke testing is to make sure that all the essential functionality works fine and without any errors, so a team of QA specialists is able to continue with more complex testing. It is really important to run such small and quick regression tests of basic functionality and identify showstoppers. Smoke testing enables testers to save time and avoid wasted time, as detecting flaws in the early stages keeps the team focused and allows them to fail and recover early. Smoke tests are created with the intention of indicating system stability and conformance to requirements. This type of functional testing may be performed both manually and with automation. Read the full article