Dry run (testing)

A dry run (or practice run) is a software testing process where the effects of a possible failure are intentionally mitigated.[1] For example, there is rsync utility for transfer data over some interface (usually Ethernet), but user can try rsync with dry-run option to check syntax and test communication without data transferring.

The usage of "dry run" in acceptance procedures (for example in factory acceptance testing) is meant as following: the factory, which is a subcontractor, must perform a complete test of the system it has to deliver before the actual acceptance by customer.[2][3]

Etymology

The 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

References
  1. "Dry Run « The Word Detective". www.word-detective.com. Retrieved 28 April 2021.
  2. Craig, Rick David; Jaskiel, Stefan P. (2002). Systematic Software Testing. Artech House. ISBN 978-1-58053-792-6.
  3. Schmidt, Richard (2013-04-30). Software Engineering: Architecture-driven Software Development. Newnes. ISBN 978-0-12-407878-9.
Look up dry run in Wiktionary, the free dictionary.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.