This document discusses xUnit test patterns and strategies for minimal test automation. It introduces the test pyramid concept of having more granular unit tests than integrated tests, which are more than user interface tests. It also provides recommendations to write tests before implementation, ensure testable design, and focus automated tests on the customer experience through examples and data-driven tests rather than fragile recorded tests. Questions are solicited at the end.

1. xUnit Test Patterns
Prepare for a tour in a test automation
field

2. Title:
xUnit Test Patterns
Author:
Gerard Meszaros
Publisher:
Addison-Wesley
Copyright Date:
2007
About

3. Summary
Test Automation isn’t bad thing. It can help you even work better.

4. Disclaimer
Test Automation does NOT override Manual Testing.

5. Test Pyramid
Martin Fowler Blog

6. Test Pyramid
Testing Pyramids

7. Test Pyramid in your current project

8. Test Pyramid Ice
Cream Cone
Testing Pyramids

9. Issue
Everything’s fine & shiny (as I hear it
in every retrospective).

10. Simple minimal test automation
strategySolution

11. ● Never
● Before implementation
● After implementation
When do you
write tests ?

12. ● Testable Design - Layered
architecture, DDD, etc.
● TDD before we write software
How do we
ensure our
software is
testable ?

13. ● Customer test suite
● Unit test suite
Minimal test
suites in story-
driven
development

14. Customer Tests
Scripted tests
Using programming language,
frameworks
Data-driven tests
Example: Table with input and
expected output columns.
Recorded tests
Existing app, Fragile tests

15. Avoid long tests
● Obscure tests
● Bad defect localization

16. Tests can give you
● Tests as documentation
● Executable user acceptance criteria (UAT)
● Good defect localization

17. Unit Tests

18. Review
Questions?
Answers.