Scenario testing
| publisher = Cem Kaner
}}</ref> These tests are usually different from test cases in that test cases are single steps whereas scenarios cover a number of steps.[1][2]
Kaner coined the phrase scenario test by October 2003.[3] He had already co-authored a book on software testing, lectured on the subject, and was a testing consultant. He commented that one of the most difficult aspects of testing was maintaining step-by-step test cases along with their expected results. His paper attempted to find a way to reduce the re-work of complicated written tests and incorporate the ease of use cases.[3]
A few months later, Buwalda wrote about a similar approach he had been using that he called "soap opera testing". Like television soap operas these tests were both exaggerated in activity and condensed in time.[1] The key to both approaches was to avoid step-by-step testing instructions with expected results and instead replaced them with a narrative that gave freedom to the tester while confining the scope of the test.[2]
See also
References
- ^ a b Buwalda, Hans (2004). "Soap Opera Testing" (PDF). Better Software (February 2004). Software Quality Engineering: 30–7. Retrieved 2011-11-16.
- ^ a b Crispin, Lisa (2009). Agile Testing: A Practical Guide for Testers and Agile Teams. Addison-Wesley. pp. 192–5. ISBN 81-317-3068-9.
{{cite book}}: Unknown parameter|coauthors=ignored (|author=suggested) (help) - ^ a b "An Introduction to Scenario Testing" (PDF). Cem Kaner. Retrieved 2009-05-07.
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |