Smoke test
From Wikipedia, the free encyclopedia
Smoke test is a term used in plumbing, electronics, and computer software development. It refers to the first test made after repairs or first assembly to provide some assurance that a device, plumbing, or software will not catastrophically fail. After the smoke test proves that the pipes will not leak or the circuit will not burn, the assembly is ready for more stressful testing.
- In a plumbing smoke test, actual smoke is forced through newly plumbed pipes to find leaks, before water is allowed to flow through the pipes.
- In electronics, a smoke test is the first time a circuit is attached to power, which will sometimes produce actual smoke if a design or wiring mistake has been made.
- In computer programming and software testing, smoke testing is a preliminary to further testing, which should reveal simple failures severe enough to reject a prospective software release. In this case, the smoke is metaphorical.
Contents |
[edit] Smoke testing of plumbing and sewer systems
Smoke testing in household and chemical plant plumbing is used to find places where pipes will spill fluid. Smoke testing of sanitary sewer systems is primarily used to find places where ground water and storm runoff can enter the sanitary sewer system.
Non-toxic smoke is used to find leaks in plumbing and sanitary sewer systems. Artificially created smoke is forced into the pipe or container. Plumes of smoke form where there are defects. It is particularly useful where completely sealing the system is not practical such as ventilated sanitary sewer systems.
When smoke testing a sanitary sewer system it is helpful partially block off the section of sewer to be tested. This can be done by using a sand bag on the end of a rope. The sand bag is lowered into the manhole and swung into position to partially block lines. Completely blocking the line can cause water to back up and prevent smoke from escaping through defects. Smoke testing may not be done after rain or when ground water is unusually high as this may also prevent detection of defects.
Large downdraft fans, usually powered by gasoline engines, are placed on top of open manholes at either end of the section to be tested. If possible all lines in the manholes except for the line between the manholes are partially blocked. Smoke is created using either a smoke bomb or liquid smoke. Smoke bombs are lit and placed on a grate or in a holder on top of each fan or the liquid smoke is injected into the fan via a heating chamber. The fans create a pressure differential that forces the artificial smoke into the sewer at a pressure just above atmospheric. With properly installed plumbing the traps will prevent the smoke from entering the house and redirected it out the plumbing vents.
Defective plumbing systems or dry traps will allow smoke to enter the inside of the house.
The area around the section being tested is searched for smoke plumes. Plumes coming from plumbing vents or the interface between the fan shroud and manhole rim are normal however smoke plumes outside of the manhole rim are not. Plumes are marked, usually with flags, and defects are noted using measurements from stationary landmarks like the corners of houses. The plumes or markers may also be photographed.
[edit] Testing in electronics and electrical engineering
The term smoke test or power on test is used in electronics and electrical engineering to refer to the first time a circuit under development is attached to power.
An electrical smoke test may be done before all the work is complete, just to ensure that there are no major flaws that would make further work pointless. For power above about 30 watts, circuit failure at first power-on sometimes literally produces smoke, most often from burning resistors, which produce a unique smell familiar to many technicians. For certain circuits, overheating and burning due to circuitry that is still not properly operating can be avoided by slowly turning up the input voltage to the unit under test by using a Variac and watching the electric current consumption. As a poor-man's Variac, a properly-sized incandescent light bulb in series with the power feed can provide a similar benefit: if the unit under test has a short circuit or other overload, the bulb will light up and provide a high resistance, limiting or preventing further damage to the unit being tested.
Overloaded integrated circuits typically produce "blue smoke" (or magic smoke). "Blue smoke" is the subject of jokes among technicians who refer to it as if it were a genie in the circuit: It's the blue smoke that makes it work—let out the blue smoke and it won't do anything.
[edit] Smoke testing in software development
Smoke testing is done by developers before the build is released or by testers before accepting a build for further testing.
In software engineering, a smoke test generally consists of a collection of tests that can be applied to a newly created or repaired computer program. Sometimes the tests are performed by the automated system that builds the final software. In this sense a smoke test is the process of validating code changes before the changes are checked into the larger product’s official source code collection. Next after code reviews, smoke testing is the most cost effective method for identifying and fixing defects in software; some even believe that it is the most effective of all.
In software testing, a smoke test is a collection of written tests that are performed on a system prior to being accepted for further testing. This is also known as a build verification test. This is a "shallow and wide" approach to the application. The tester "touches" all areas of the application without getting too deep, looking for answers to basic questions like, "Can I launch the test item at all?", "Does it open to a window?", "Do the buttons on the window do things?". There is no need to get down to field validation or business flows. If you get a "No" answer to basic questions like these, then the application is so badly broken, there's effectively nothing there to allow further testing. These written tests can either be performed manually or using an automated tool. When automated tools are used, the tests are often initiated by the same process that generates the build itself.
