1. Test Plans Making the world safe for software

2. Why?

3. Why?
It’s really

4. Why?
It’s really, really

5. Why?
It’s really, really, really

6. Why?
It’s really, really, really simple…

7. If it ain’t tested, it is broken.
Why?
It’s really, really, really simple…
If it ain’t tested, it is broken.

8. How they are used in industry

9. How they are used in industry
Very formal, very serious things

10. How they are used in industry
Very formal, very serious things
Can be literally hundreds of pages long

11. How they are used in industry
Very formal, very serious things
Can be literally hundreds of pages long
Often have a very large & talented team of engineers working on it

12. How they are used in industry
Very formal, very serious things
Can be literally hundreds of pages long
Often have a very large & talented team of engineers working on it
No worries, we’re not going there…

13. How we will use them

14. How we will use them
An outline of what you need to do to make sure your software does what it is supposed to do.

15. How we will use them
An outline of what you need to do to make sure your software does what it is supposed to do.
What goes in it?

16. How we will use them
An outline of what you need to do to make sure your software does what it is supposed to do.
What goes in it?
Team member’s names

17. How we will use them
An outline of what you need to do to make sure your software does what it is supposed to do.
What goes in it?
Team member’s names
Program/project name (HelloWorld, HelloUser, etc)

18. How we will use them
An outline of what you need to do to make sure your software does what it is supposed to do.
What goes in it?
Team member’s names
Program/project name (HelloWorld, HelloUser, etc)
Flowchart (attached)

19. How we will use them
An outline of what you need to do to make sure your software does what it is supposed to do.
What goes in it?
Team member’s names
Program/project name (HelloWorld, HelloUser, etc)
Flowchart (attached)
Test cases

20. What are test cases?

21. What are test cases?
Input, actions, events and the associated expected response

22. What are test cases?
Input, actions, events and the associated expected response
Used to determine if the program works

23. What are test cases?
Input, actions, events and the associated expected response
Used to determine if the program works
Testing sequence:

24. What are test cases?
Input, actions, events and the associated expected response
Used to determine if the program works
Testing sequence:
Known good input, etc.

25. What are test cases?
Input, actions, events and the associated expected response
Used to determine if the program works
Testing sequence:
Known good input, etc.
Reasonable but invalid input, etc.

26. What are test cases?
Input, actions, events and the associated expected response
Used to determine if the program works
Testing sequence:
Known good input, etc.
Reasonable but invalid input, etc.
Total obvious and evil garbage

27. How do I come up with my test cases?

28. How do I come up with my test cases?
Basic job is to become evil!

29. How do I come up with my test cases?
Basic job is to become evil!
Try to figure out as many ways as possible to break and destroy your program as you can.

30. How do I come up with my test cases?
Basic job is to become evil!
Try to figure out as many ways as possible to break and destroy your program as you can.
Pretend you are a user (not the designer) … what will/can they do?

31. How do I come up with my test cases?
Basic job is to become evil!
Try to figure out as many ways as possible to break and destroy your program as you can.
Pretend you are a user (not the designer) … what will/can they do?
Start with what you expect and move towards evilness. 

32. How do I come up with my test cases?

33. How do I come up with my test cases?
Look at your flowchart … it is your friend

34. How do I come up with my test cases?
Look at your flowchart … it is your friend
Any decision is a danger spot

35. How do I come up with my test cases?
Look at your flowchart … it is your friend
Any decision is a danger spot
Decision question really what I want to be asking?

36. How do I come up with my test cases?
Look at your flowchart … it is your friend
Any decision is a danger spot
Decision question really what I want to be asking?
Do I have the “false” path covered right and completely?

37. How do I come up with my test cases?
Look at your flowchart … it is your friend
Any decision is a danger spot
Decision question really what I want to be asking?
Do I have the “false” path covered right and completely?
For instance: if user input is “yes”

38. How do I come up with my test cases?
Look at your flowchart … it is your friend
Any decision is a danger spot
Decision question really what I want to be asking?
Do I have the “false” path covered right and completely?
For instance: if user input is “yes”
“yes” is the true case

39. How do I come up with my test cases?
Look at your flowchart … it is your friend
Any decision is a danger spot
Decision question really what I want to be asking?
Do I have the “false” path covered right and completely?
For instance: if user input is “yes”
“yes” is the true case
What is the false case?

40. How do I come up with my test cases?
Look at your flowchart … it is your friend
Any decision is a danger spot
Decision question really what I want to be asking?
Do I have the “false” path covered right and completely?
For instance: if user input is “yes”
“yes” is the true case
What is the false case?
The obvious one is “no”

41. How do I come up with my test cases?
Look at your flowchart … it is your friend
Any decision is a danger spot
Decision question really what I want to be asking?
Do I have the “false” path covered right and completely?
For instance: if user input is “yes”
“yes” is the true case
What is the false case?
The obvious one is “no”
But…what about “Yes” or “YES” or “yEs” or “Y” or … you get the idea…

42. How do I come up with my test cases?
Look at your flowchart … it is your friend
Any decision is a danger spot
Decision question really what I want to be asking?
Do I have the “false” path covered right and completely?
For instance: if user input is “yes”
“yes” is the true case
What is the false case?
The obvious one is “no”
But…what about “Yes” or “YES” or “yEs” or “Y” or … you get the idea…
Will your software do the “right” thing?

43. How do I come up with my test cases?

44. How do I come up with my test cases?
Look at your flowchart … continued

45. How do I come up with my test cases?
Look at your flowchart … continued
Any loop is a danger spot

46. How do I come up with my test cases?
Look at your flowchart … continued
Any loop is a danger spot
Does my loop have an exit condition?

47. How do I come up with my test cases?
Look at your flowchart … continued
Any loop is a danger spot
Does my loop have an exit condition?
Is it “going” the right way?

48. How do I come up with my test cases?
Look at your flowchart … continued
Any loop is a danger spot
Does my loop have an exit condition?
Is it “going” the right way?
Incrementing when I wanted to decrement? Or vice-versa…

49. How do I come up with my test cases?

50. How do I come up with my test cases?
Look at your flowchart … continued

51. How do I come up with my test cases?
Look at your flowchart … continued
Look closely at any user input

52. How do I come up with my test cases?
Look at your flowchart … continued
Look closely at any user input
Is it being stored properly? … at all???

53. How do I come up with my test cases?
Look at your flowchart … continued
Look closely at any user input
Is it being stored properly? … at all???
Is it being handled correctly?

54. How do I come up with my test cases?
Look at your flowchart … continued
Look closely at any user input
Is it being stored properly? … at all???
Is it being handled correctly?
Remember … users are EVIL

55. Your Task

56. Your Task
Put together a test plan to test the “File Open” dialog of WordPad

57. Your Task
Put together a test plan to test the “File Open” dialog of WordPad
Consider it’s capabilities and intended use

58. Your Task
Put together a test plan to test the “File Open” dialog of WordPad
Consider it’s capabilities and intended use
Remember the testing sequence:

59. Your Task
Put together a test plan to test the “File Open” dialog of WordPad
Consider it’s capabilities and intended use
Remember the testing sequence:
Known good input

60. Your Task
Put together a test plan to test the “File Open” dialog of WordPad
Consider it’s capabilities and intended use
Remember the testing sequence:
Known good input
Reasonable but invalid input

61. Your Task
Put together a test plan to test the “File Open” dialog of WordPad
Consider it’s capabilities and intended use
Remember the testing sequence:
Known good input
Reasonable but invalid input
Total, obvious and evil garbage

62. Your Task
Put together a test plan to test the “File Open” dialog of WordPad
Consider it’s capabilities and intended use
Remember the testing sequence:
Known good input
Reasonable but invalid input
Total, obvious and evil garbage
Turn in at end of period…all team member names at top.
…go…

63. WordPad Test Cases – Known Good

64. WordPad Test Cases – Known Good
1. Action: Double-click on text file appearing in “Open” dialog window.
Expected Response: WordPad will open the file
2. Action: Type name of text file appearing in “Open” dialog window, click “Open” button.
3. Action: Type name of text file appearing in “Open” dialog window, hit enter.
4. Action: Existing file not in window. Navigate to it using “Look in” pull-down menu.
Expected Response: File will appear in “Open” dialog window
5. Action: Existing file not in window. Navigate to it using the “Up One Level” button and by double clicking on
folders in the “Open” dialog window.
6. Action: File appears in “Open” dialog window. Select different file type in “Files of type” pull-down menu.
Expected Response: File will no longer appear in “Open” dialog window
. . . There are about a billion more . . .

65. WordPad Test Cases – Known Good
1. Action: Double-click on text file appearing in “Open” dialog window.
Expected Response: WordPad will open the file
2. Action: Type name of text file appearing in “Open” dialog window, click “Open” button.
3. Action: Type name of text file appearing in “Open” dialog window, hit enter.
4. Action: Existing file not in window. Navigate to it using “Look in” pull-down menu.
Expected Response: File will appear in “Open” dialog window
5. Action: Existing file not in window. Navigate to it using the “Up One Level” button and by double clicking on
folders in the “Open” dialog window.
6. Action: File appears in “Open” dialog window. Select different file type in “Files of type” pull-down menu.
Expected Response: File will no longer appear in “Open” dialog window
. . . There are about a billion more . . .

66. WordPad Test Cases – Known Good
1. Action: Double-click on text file appearing in “Open” dialog window.
Expected Response: WordPad will open the file
2. Action: Type name of text file appearing in “Open” dialog window, click “Open” button.
3. Action: Type name of text file appearing in “Open” dialog window, hit enter.
4. Action: Existing file not in window. Navigate to it using “Look in” pull-down menu.
Expected Response: File will appear in “Open” dialog window
5. Action: Existing file not in window. Navigate to it using the “Up One Level” button and by double clicking on
folders in the “Open” dialog window.
6. Action: File appears in “Open” dialog window. Select different file type in “Files of type” pull-down menu.
Expected Response: File will no longer appear in “Open” dialog window
. . . There are about a billion more . . .

67. WordPad Test Cases – Known Good
1. Action: Double-click on text file appearing in “Open” dialog window.
Expected Response: WordPad will open the file
2. Action: Type name of text file appearing in “Open” dialog window, click “Open” button.
3. Action: Type name of text file appearing in “Open” dialog window, hit enter.
4. Action: Existing file not in window. Navigate to it using “Look in” pull-down menu.
Expected Response: File will appear in “Open” dialog window
5. Action: Existing file not in window. Navigate to it using the “Up One Level” button and by double clicking on
folders in the “Open” dialog window.
6. Action: File appears in “Open” dialog window. Select different file type in “Files of type” pull-down menu.
Expected Response: File will no longer appear in “Open” dialog window
. . . There are about a billion more . . .

68. WordPad Test Cases – Known Good
1. Action: Double-click on text file appearing in “Open” dialog window.
Expected Response: WordPad will open the file
2. Action: Type name of text file appearing in “Open” dialog window, click “Open” button.
3. Action: Type name of text file appearing in “Open” dialog window, hit enter.
4. Action: Existing file not in window. Navigate to it using “Look in” pull-down menu.
Expected Response: File will appear in “Open” dialog window
5. Action: Existing file not in window. Navigate to it using the “Up One Level” button and by double clicking on
folders in the “Open” dialog window.
6. Action: File appears in “Open” dialog window. Select different file type in “Files of type” pull-down menu.
Expected Response: File will no longer appear in “Open” dialog window
. . . There are about a billion more . . .

69. WordPad Test Cases – Known Good
1. Action: Double-click on text file appearing in “Open” dialog window.
Expected Response: WordPad will open the file
2. Action: Type name of text file appearing in “Open” dialog window, click “Open” button.
3. Action: Type name of text file appearing in “Open” dialog window, hit enter.
4. Action: Existing file not in window. Navigate to it using “Look in” pull-down menu.
Expected Response: File will appear in “Open” dialog window
5. Action: Existing file not in window. Navigate to it using the “Up One Level” button and by double clicking on
folders in the “Open” dialog window.
6. Action: File appears in “Open” dialog window. Select different file type in “Files of type” pull-down menu.
Expected Response: File will no longer appear in “Open” dialog window
. . . There are about a billion more . . .

70. WordPad Test Cases – Known Good
1. Action: Double-click on text file appearing in “Open” dialog window.
Expected Response: WordPad will open the file
2. Action: Type name of text file appearing in “Open” dialog window, click “Open” button.
3. Action: Type name of text file appearing in “Open” dialog window, hit enter.
4. Action: Existing file not in window. Navigate to it using “Look in” pull-down menu.
Expected Response: File will appear in “Open” dialog window
5. Action: Existing file not in window. Navigate to it using the “Up One Level” button and by double clicking on
folders in the “Open” dialog window.
6. Action: File appears in “Open” dialog window. Select different file type in “Files of type” pull-down menu.
Expected Response: File will no longer appear in “Open” dialog window
. . . There are about a billion more . . .

71. WordPad Test Cases – Reasonable but Invalid

72. WordPad Test Cases – Reasonable but Invalid
7. Action: After completing #6 above (file name does not appear in “Open” dialog window),
type in name of file in “File name” edit field, click “Open” button.
Expected Response: WordPad will open the file
8. Action: Type name of non-existent file in “File name” edit field, click “Open” button.
Expected Response: WordPad will display “File not found” error message
9. Action: Double-click on text file appearing in “Open” dialog window.
10. Action: With no text in the “File name” edit field, click the “Open” button.
Expected Response: WordPad will do nothing
. . . There are about a billion more . . .

73. WordPad Test Cases – Reasonable but Invalid
7. Action: After completing #6 above (file name does not appear in “Open” dialog window),
type in name of file in “File name” edit field, click “Open” button.
Expected Response: WordPad will open the file
8. Action: Type name of non-existent file in “File name” edit field, click “Open” button.
Expected Response: WordPad will display “File not found” error message
9. Action: Double-click on text file appearing in “Open” dialog window.
10. Action: With no text in the “File name” edit field, click the “Open” button.
Expected Response: WordPad will do nothing
. . . There are about a billion more . . .

74. WordPad Test Cases – Reasonable but Invalid
7. Action: After completing #6 above (file name does not appear in “Open” dialog window),
type in name of file in “File name” edit field, click “Open” button.
Expected Response: WordPad will open the file
8. Action: Type name of non-existent file in “File name” edit field, click “Open” button.
Expected Response: WordPad will display “File not found” error message
9. Action: Double-click on text file appearing in “Open” dialog window.
10. Action: With no text in the “File name” edit field, click the “Open” button.
Expected Response: WordPad will do nothing
. . . There are about a billion more . . .

75. WordPad Test Cases – Reasonable but Invalid
7. Action: After completing #6 above (file name does not appear in “Open” dialog window),
type in name of file in “File name” edit field, click “Open” button.
Expected Response: WordPad will open the file
8. Action: Type name of non-existent file in “File name” edit field, click “Open” button.
Expected Response: WordPad will display “File not found” error message
9. Action: Double-click on text file appearing in “Open” dialog window.
10. Action: With no text in the “File name” edit field, click the “Open” button.
Expected Response: WordPad will do nothing
. . . There are about a billion more . . .

76. WordPad Test Cases – Reasonable but Invalid
7. Action: After completing #6 above (file name does not appear in “Open” dialog window),
type in name of file in “File name” edit field, click “Open” button.
Expected Response: WordPad will open the file
8. Action: Type name of non-existent file in “File name” edit field, click “Open” button.
Expected Response: WordPad will display “File not found” error message
9. Action: Double-click on text file appearing in “Open” dialog window.
10. Action: With no text in the “File name” edit field, click the “Open” button.
Expected Response: WordPad will do nothing
. . . There are about a billion more . . .

77. WordPad Test Cases – Obvious Garbage

78. WordPad Test Cases – Obvious Garbage
11. Action: In the “File name” edit field, type in 256 of the following in a row: \0
and click the “Open” button
Expected Response: WordPad will display “\0\0\0\0\0…\0 The above file name is invalid” error message
12. Action: Type in the name of a folder appearing in the “Open” dialog window.
Expected Response: WordPad display the contents of that folder in the “Open” dialog window
13. Action: Select “Rich Text Format (*.rtf)” in the “Files of type” pull-down menu. Ensure at least rtf appear in
the “Open” dialog window. Enter the text “*.rtf” (not including double-quotes) in the “File name”
edit field. Click the “Open” button.
Expected Response: WordPad will do nothing
14. Action: Enter the following text in the “File name” edit field: *.exe
Locate an executable file (file name ends with .exe). Double-click on it.
Expected Response: WordPad opens the file, displays strange symbols but doesn’t crash
. . . There are about a billion more . . .

79. WordPad Test Cases – Obvious Garbage
11. Action: In the “File name” edit field, type in 256 of the following in a row: \0
and click the “Open” button
Expected Response: WordPad will display “\0\0\0\0\0…\0 The above file name is invalid” error message
12. Action: Type in the name of a folder appearing in the “Open” dialog window.
Expected Response: WordPad display the contents of that folder in the “Open” dialog window
13. Action: Select “Rich Text Format (*.rtf)” in the “Files of type” pull-down menu. Ensure at least rtf appear in
the “Open” dialog window. Enter the text “*.rtf” (not including double-quotes) in the “File name”
edit field. Click the “Open” button.
Expected Response: WordPad will do nothing
14. Action: Enter the following text in the “File name” edit field: *.exe
Locate an executable file (file name ends with .exe). Double-click on it.
Expected Response: WordPad opens the file, displays strange symbols but doesn’t crash
. . . There are about a billion more . . .

80. WordPad Test Cases – Obvious Garbage
11. Action: In the “File name” edit field, type in 256 of the following in a row: \0
and click the “Open” button
Expected Response: WordPad will display “\0\0\0\0\0…\0 The above file name is invalid” error message
12. Action: Type in the name of a folder appearing in the “Open” dialog window.
Expected Response: WordPad display the contents of that folder in the “Open” dialog window
13. Action: Select “Rich Text Format (*.rtf)” in the “Files of type” pull-down menu. Ensure at least rtf appear in
the “Open” dialog window. Enter the text “*.rtf” (not including double-quotes) in the “File name”
edit field. Click the “Open” button.
Expected Response: WordPad will do nothing
14. Action: Enter the following text in the “File name” edit field: *.exe
Locate an executable file (file name ends with .exe). Double-click on it.
Expected Response: WordPad opens the file, displays strange symbols but doesn’t crash
. . . There are about a billion more . . .

81. WordPad Test Cases – Obvious Garbage
11. Action: In the “File name” edit field, type in 256 of the following in a row: \0
and click the “Open” button
Expected Response: WordPad will display “\0\0\0\0\0…\0 The above file name is invalid” error message
12. Action: Type in the name of a folder appearing in the “Open” dialog window.
Expected Response: WordPad display the contents of that folder in the “Open” dialog window
13. Action: Select “Rich Text Format (*.rtf)” in the “Files of type” pull-down menu. Ensure at least rtf appear in
the “Open” dialog window. Enter the text “*.rtf” (not including double-quotes) in the “File name”
edit field. Click the “Open” button.
Expected Response: WordPad will do nothing
14. Action: Enter the following text in the “File name” edit field: *.exe
Locate an executable file (file name ends with .exe). Double-click on it.
Expected Response: WordPad opens the file, displays strange symbols but doesn’t crash
. . . There are about a billion more . . .

82. WordPad Test Cases – Obvious Garbage
11. Action: In the “File name” edit field, type in 256 of the following in a row: \0
and click the “Open” button
Expected Response: WordPad will display “\0\0\0\0\0…\0 The above file name is invalid” error message
12. Action: Type in the name of a folder appearing in the “Open” dialog window.
Expected Response: WordPad display the contents of that folder in the “Open” dialog window
13. Action: Select “Rich Text Format (*.rtf)” in the “Files of type” pull-down menu. Ensure at least rtf appear in
the “Open” dialog window. Enter the text “*.rtf” (not including double-quotes) in the “File name”
edit field. Click the “Open” button.
Expected Response: WordPad will do nothing
13. Action: Enter the following text in the “File name” edit field: *.exe
Locate an executable file (file name ends with .exe). Double-click on it.
Expected Response: WordPad opens the file, displays strange symbols but doesn’t crash
. . . There are about a billion more . . .

83. Clear and Unclear Windows