Testing is done to either verify expected functionality or learn something new. It involves observing a system under different controlled conditions to check actual responses against expectations. There are various types of testing like unit, functional, acceptance, and performance testing. Testing is important to do early in development to define requirements and catch issues early. It provides feedback to improve the system through iterations. Well-structured automated tests are key to ensuring quality and allowing refactoring.

2. Free beer* and testing
*Free beer not included

3. Why Test?

4. We test to either...

5. verify what is expected...
We test to either...

6. verify what is expected...
We test to either...
or to learn something completely new

7. <insert cliche stock photo here>

8. verification...

9. ...asserting actual response against expected outcome

10. requirements and specifications...

11. ...what we normally think of as Testing

12. https://msdn.microsoft.com
Unit Tests
Functional Tests
Acceptance Tests
Performance Tests SLAs

13. ...exploratory testing

14. ...learning something completely new

15. structured exploratory testing

16. answering a specific

17. “What does the
system do under
these
conditions?”

18. “What is the user’s
experience when
making a transaction
with a gift card?”

19. “How many
transactions can it
handle?”

20. ad hoc
testing

21. What is Testing?

22. system under test

23. Testing is observation or inspection of the
system under test in different, controlled conditions
system under test

24. only one change at a time
system under test

25. Quantitative
(Measurable)
system under test

26. Qualitative
(Descriptive)
system under test

27. Testing is the Feed

28. Testing is the Feed back into the next iteration...

29. ...the bringing of the “outside” into the system

30. Testing is the cornerstone of...

31. DRUMMER WANTEDhttps://www.facebook.com/TheEmpiricalMethod

33. XPtest driven developmenttest driven development

34. XPtest driven development
start with what it should do

35. XPtest driven development
start with what it should do

36. XPtest driven development
unit through integration

37. BDDacceptance test driven development
executing requirements
f
u
l
l
s
t
a
c
k

38. When to Test?

39. As early as possible

40. like when the requirements are being specified

41. write once, test once

42. did something change?

43. did something change?
analyze impact of change to system

44. well structured code (SOLID) eliminates dependency
between conditions and minimizes tests
use impact and
conditional
analysis to
determine the
structure of your
code

45. the cost of development
AUTOMATION

46. How to test?

47. testing is a craft...

48. analyze relevant conditions and their dependencies
analyze

49. design minimum number of test scripts to exercise all
conditions and dependencies
design

50. execute

51. Equivalence Class Partitioning
B
o
u
n
d
a
r
y
v
a
l
u
e
a
n
a
l
y
s
i
s

52. GIVE
NWHE
NTHEN

53. defined behavior
GIVE
NWHE
NTHEN

54. well written tests are
more important than
well written code
because with them the
system is defined and
can always be recreated
...or refactored
the system is defined by its tests,
NOT its implementing software

55. the end.