This is a "shallow and wide" approach to testing. A tester "touches" all major areas of the application, performs surface testing just looking for answers to basic questions. Smoke testing hasn’t to be exhaustive; however, it should be sufficient enough. As the result of software testing, the tester can decide whether the project version is stable enough to be passed to the next, more careful testing phase.
Installation errors: If the software can’t be installed, its testing is likely to be impossible at all.
Failure to connect to a database that is relevant to the client-server architecture. Subsorts of smoke testing are «Build Verification Testing» or «Acceptance Testing» performed by the testing team at the functional level. According to its results, the conclusion is made whether the installed software version is accepted for testing, operation, or delivery to the customer.
Smoke testing is the most cost-effective method for identifying and fixing software defects; and some people even believe that it is the most effective way of testing at all.
So, let’s mark out Smoke testing highlights:
- Smoke test is performed to check the assembly’s “level of health”.
- It is also known as shallow and wide trials, i.e. tests covering all functionality of a software application.
- Smoke test is a kind of the first step of testing. After this, we usually perform other kinds of functional and system testing, including regression testing.