What is a smoke test and what is it eaten with?

K

khamitov_dima2017-03-16 03:30:51

linux

khamitov_dima, 2017-03-16 03:30:51

What is a smoke test? Google gave only a brief formulation, but I would like with specific examples, literature, etc. How can I run these tests (what commands in the shell) in different unix-like OSes for different utilities. As far as I understand, for each program there is a certain set of commands ( tool -h or -version ), and by checking the performance of such a manpage, we can say that this utility has passed the smoke test or not.
I apologize in advance if I wrote nonsense. Thanks

Reply

Answer the question

In order to leave comments, you need to log in

4 answer(s)

M

mayor-jojo, 2017-03-16
@mayor-jojo

Have you tried to google the links?
Wikipedia Smoke test

C

CityCat4, 2017-03-16
@CityCat4

"Checking for smoke" :) The first inclusion of a complex device, a global complex test of a large project, etc.
Where does this name come from? The first inclusion of a complex expensive device is done with all the covers removed, so that it can be immediately seen if there is a spark somewhere, a bad contact, if smoke comes from somewhere due to the fact that some element turned out to be of poor quality.

D

Dmitry, 2017-03-16
@EvilsInterrupt

Smoke is a smoky test. The name came from electronics. When they repair equipment, they carefully take the plug and slowly, carefully connect it to the network. If it doesn’t smoke, then in the first approximation everything is ok.
So it is in programming. Any changed/added/removed line of code can break the product. And in order to find out about this very quickly, they create tests that cover as much functionality as possible in the product. They have no task to localize the cause of the breakdown. They have a different task: "does it somehow work or not?"

N

Nazar Mokrinsky, 2017-03-16
@nazarpc

These are tests that often include a relatively large number of project subsystems and are used for general health assessment.
I would say something like an integration/system test, but more selective. For example, a widget is connected on a web page and it is checked whether the size of this widget is correct or not. If not, then obviously something went wrong :) tool -h, in principle, can also be such a check.
The bottom line is to quickly check whether everything has fallen apart to hell (it didn’t burn out, it smoked, hence the smoke).