1. A Simple Intro To

2. quick
questions
to start!

3. had a client who
knew what he
needed?
question 1

4. been in a project
with no change in
requirements?
question 2

5. predicted every
problem 3 months
in advance?
question 3

7. Agile Context
of Testing

8. respond to change!

9. A
B

10. A
B
C

11. change
risk

12. reduce the risk!

13. reduce the risk!
use the
agile
iterative
cycle

14. reduce the risk!
test
continuously
fast feedback

16. know what works at
any given moment

19. Types of Tests

20. Functional Tests
Examples
Story Tests
Prototypes
Simulations
Unit Tests
Component Tests
Exploratoy Testing
Scenarios
Usability Testing
UAT
A/B
Performance & Load Testing
Security Testing
“ility Testing”
Automated
& Manual
Automated
Manual
Tools
Q2 Q3
Q1 Q4
Business Facing
Technology Facing
SupportingtheTeam
CritiqueProduct

21. Functional Tests
Examples
Story Tests
Prototypes
Simulations
Unit Tests
Component Tests
Exploratoy Testing
Scenarios
Usability Testing
UAT
A/B
Performance & Load Testing
Security Testing
“ility Testing”
Automated
& Manual
Automated
Manual
Tools
Q2 Q3
Q1 Q4
Business Facing
Technology Facing
SupportingtheTeam
CritiqueProduct

22. Coding
Unit Testing
Program Unit
Design
Physical Design
Logical Design
User
Requirements
Integration
Testing
System Testing
Acceptance
Testing
Verifies
Verifies
Verifies
Verifies

23. hard
expensive
slow
easy
cheap
fast
more
less
UI
Integration
Unit

24. What Is A
Unit Test?

25. Unit Tests
• Tests a single unit of code (typically a method)
• Tests the unit of code in ISOLATION
• Tests that the code behaves as expected

26. Unit Tests
• It’s still code
• Code that tests code
• Exercise SUT, check behaviour
• Concepts: Test Class, Test Method

27. Test Structure

28. ARRANGE ACT ASSERT

29. Test Structure
ARRANGE
ACT
ASSERT

30. Unit Tests
• Should be fast (< 10 ms)
• Should be consistent (same result always)
• Should run in memory (no db, file access)
• Should run in any order (no dependencies on other
tests)

31. Impacts
• Fast Feedback
• Cleaner design
• Code and componente decoupling
• Confidence
• Executable documentation, with usage samples
• Reduce regression

33. TDD vs.
Unit Testing

34. unit testing
is not
TDD

35. TDD
is
unit testing
(in a particular order)

37. TDD in
three
steps

38. TDD is
different approach
to coding

39. Demo

40. https://github.com/MiguelAlho/TddCalculator

41. References

42. Books
• Pragmatic Unit Testing In C# with Nunit
• Growing software guided by tests
• The art of unit Testing
• Testable Javascript
• Quality Code
• Xunit Patterns