Smoke Testing

Smoke testing is focused to verify the functional requirements and software build and ensure that they are in accordance with the software development and software testing process.  This testing method is carried out in the initial stages of the software testing process and makes sure that the functional testing can be carried out in a streamlined manner. In this article, you will know about the techniques and advantages of smoke testing.

  There aren't many topics in testing quality assurance that create such confusion and miscommunication as the smoke test and Sanity testing. Both names appear to refer to very different procedures which they are, and indeed! But many people remain confused, as the distinction between them isn't as obvious. When you're creating an application for mobile devices or a web-based service or even the Internet of Things, you likely will conduct smoke and sanity tests along the way and likely in the same order. Smoke testing is more general, high-level method of testing, whereas the sanity test is more specific and focuses on the logical aspects. Let's look at each one more in depth: Smoke testing The first thing you might be asking yourself is why the name "smoke test"? It's certainly a bit odd however, it is logical. The term is derived from hardware testing. Test engineers that turn on a server, PC or storage appliance , look for smoke that is coming f...

It is a testing method that ascertains whether a deployed software build is stable or not. The basic functionality of the build is tested. If a build is declared unstable, that means the test has failed, and it will be tested until the build passes the smoke test. https://articlescad.com/what-is-smoke-testing-and-what-are-its-characteristics-50058.html