A dry run (or practice run) is a software testing process used to make sure that a system works correctly and will not result in severe failure.[1] For example, rsync, a utility for transferring and synchronizing data between networked computers or storage drives, has a "dry-run" option users can use to check that their command-line arguments are valid and to simulate what would happen when actually copying the data.
In acceptance procedures (such as factory acceptance testing, for example), a "dry run" is when the factory, a subcontractor, performs a complete test of the system it has to deliver before it is actually accepted by the customer.[2][3]
Etymology
editThe term dry run appears to have originated from fire departments in the US. In order to practice, they would carry out dispatches of the fire brigade where water was not pumped. A run with real fire and water was referred to as a wet run. The more general usage of the term seems to have arisen from widespread use by the United States Armed Forces during World War II.[1]
See also
editReferences
edit- ^ a b "Dry Run « The Word Detective". www.word-detective.com. Retrieved 28 April 2021.
- ^ Craig, Rick David; Jaskiel, Stefan P. (2002). Systematic Software Testing. Artech House. ISBN 978-1-58053-792-6.
- ^ Schmidt, Richard (2013-04-30). Software Engineering: Architecture-driven Software Development. Newnes. ISBN 978-0-12-407878-9.
External links
edit
 | This industry-related article is a stub. You can help Wikipedia by expanding it. |
 | This computer-programming-related article is a stub. You can help Wikipedia by expanding it. |