56:
coined the phrase scenario test by
October 2003. 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
64:
A few months later, Hans
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. The key to both approaches was to avoid step-by-step testing instructions with
41:: hypothetical stories to help the tester work through a complex problem or test system. The ideal scenario test is a credible, complex, compelling or motivating story; the outcome of which is easy to evaluate. These tests are usually different from
78:
In this method only those sets of realistic, user activities that cover several components in the system are used as scenario tests. Development of system scenario can be done using:
271:
222:
65:
expected results and instead replaced them with a narrative that gave freedom to the tester while confining the scope of the test.
521:
264:
546:
485:
577:
490:
257:
531:
480:
450:
392:
178:
410:
405:
125:
455:
445:
38:
440:
435:
425:
369:
314:
304:
495:
470:
430:
420:
364:
106:
In this method the focus is on how a user uses the system with different roles and environment.
505:
331:
299:
294:
218:
92:
475:
460:
415:
341:
326:
280:
87:
82:
34:
500:
551:
526:
465:
374:
346:
214:
571:
541:
536:
379:
309:
556:
400:
336:
115:
150:
45:
in that test cases are single steps whereas scenarios cover a number of steps.
120:
17:
53:
42:
58:
249:
253:
211:
Agile
Testing: A Practical Guide for Testers and Agile Teams
514:
388:
357:
287:
188:(February 2004). Software Quality Engineering: 30–7
204:
202:
172:
170:
265:
145:
143:
141:
27:Software testing activity that uses scenarios
8:
272:
258:
250:
240:Software Testing:Principles and Practice
137:
209:Crispin, Lisa; Gregory, Janet (2009).
151:"An Introduction to Scenario Testing"
7:
97:Implementation story from customers
25:
238:Gopalaswamy, Srinivasan Desikan.
102:Use-case and role-based scenarios
522:Graphical user interface testing
1:
547:Software reliability testing
486:Software performance testing
594:
389:Testing types, techniques,
532:Orthogonal array testing
481:Smoke testing (software)
451:Dynamic program analysis
177:Buwalda, Hans (2004).
411:Compatibility testing
126:Session-based testing
456:Installation testing
446:Differential testing
179:"Soap Opera Testing"
441:Development testing
436:Destructive testing
426:Conformance testing
370:Integration testing
315:Model-based testing
305:Exploratory testing
37:activity that uses
496:Symbolic execution
471:Regression testing
431:Continuous testing
421:Concurrent testing
365:Acceptance testing
288:The "box" approach
217:. pp. 192–5.
93:Business verticals
565:
564:
506:Usability testing
332:White-box testing
300:All-pairs testing
295:Black-box testing
88:State transitions
16:(Redirected from
585:
578:Software testing
476:Security testing
461:Negative testing
416:Concolic testing
342:Mutation testing
327:Grey-box testing
320:Scenario testing
281:Software testing
274:
267:
260:
251:
244:
243:
235:
229:
228:
206:
197:
196:
194:
193:
183:
174:
165:
164:
162:
161:
155:
147:
74:System scenarios
35:software testing
31:Scenario testing
21:
593:
592:
588:
587:
586:
584:
583:
582:
568:
567:
566:
561:
510:
501:Test automation
390:
384:
353:
283:
278:
248:
247:
237:
236:
232:
225:
208:
207:
200:
191:
189:
186:Better Software
181:
176:
175:
168:
159:
157:
153:
149:
148:
139:
134:
112:
104:
76:
71:
51:
28:
23:
22:
15:
12:
11:
5:
591:
589:
581:
580:
570:
569:
563:
562:
560:
559:
554:
552:Stress testing
549:
544:
539:
534:
529:
527:Manual testing
524:
518:
516:
512:
511:
509:
508:
503:
498:
493:
491:Stress testing
488:
483:
478:
473:
468:
466:Random testing
463:
458:
453:
448:
443:
438:
433:
428:
423:
418:
413:
408:
403:
397:
395:
386:
385:
383:
382:
377:
375:System testing
372:
367:
361:
359:
358:Testing levels
355:
354:
352:
351:
350:
349:
347:Static testing
344:
339:
329:
324:
323:
322:
317:
312:
307:
302:
291:
289:
285:
284:
279:
277:
276:
269:
262:
254:
246:
245:
230:
223:
215:Addison-Wesley
198:
166:
136:
135:
133:
130:
129:
128:
123:
118:
111:
108:
103:
100:
99:
98:
95:
90:
85:
75:
72:
70:
67:
50:
47:
26:
24:
14:
13:
10:
9:
6:
4:
3:
2:
590:
579:
576:
575:
573:
558:
555:
553:
550:
548:
545:
543:
540:
538:
535:
533:
530:
528:
525:
523:
520:
519:
517:
513:
507:
504:
502:
499:
497:
494:
492:
489:
487:
484:
482:
479:
477:
474:
472:
469:
467:
464:
462:
459:
457:
454:
452:
449:
447:
444:
442:
439:
437:
434:
432:
429:
427:
424:
422:
419:
417:
414:
412:
409:
407:
404:
402:
399:
398:
396:
394:
387:
381:
378:
376:
373:
371:
368:
366:
363:
362:
360:
356:
348:
345:
343:
340:
338:
335:
334:
333:
330:
328:
325:
321:
318:
316:
313:
311:
308:
306:
303:
301:
298:
297:
296:
293:
292:
290:
286:
282:
275:
270:
268:
263:
261:
256:
255:
252:
241:
234:
231:
226:
224:81-317-3068-9
220:
216:
212:
205:
203:
199:
187:
180:
173:
171:
167:
152:
146:
144:
142:
138:
131:
127:
124:
122:
119:
117:
114:
113:
109:
107:
101:
96:
94:
91:
89:
86:
84:
81:
80:
79:
73:
68:
66:
62:
60:
55:
48:
46:
44:
40:
36:
32:
19:
18:Test scenario
542:Soak testing
537:Pair testing
380:Unit testing
319:
310:Fuzz testing
239:
233:
210:
190:. Retrieved
185:
158:. Retrieved
105:
77:
63:
52:
30:
29:
557:Web testing
401:A/B testing
337:API testing
156:. Cem Kaner
116:Test script
83:Story lines
192:2011-11-16
160:2009-05-07
132:References
121:Test suite
43:test cases
406:Benchmark
59:use cases
54:Cem Kaner
39:scenarios
572:Category
515:See also
110:See also
393:tactics
69:Methods
49:History
221:
182:(PDF)
154:(PDF)
33:is a
391:and
219:ISBN
574::
213:.
201:^
184:.
169:^
140:^
61:.
273:e
266:t
259:v
242:.
227:.
195:.
163:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.