This document discusses xUnit test patterns, including definitions of unit testing and non-unit testing, the phases of testing like test organization and smells, and types of smells. It covers test phases, organizing test suites and test cases, different types of smells at the code, behavior, and project levels, and examples of code smells.

1. xUnit Test Patterns
Test organization; Smells;

2. ● Definitions
● Test phases
● Test organization
● Smells’ types
Agenda

3. SUT = Subject Under Test
● Unit testing
○ Procedural programming - procedure
○ Functional programming - function
○ OOP - object
● Non-unit testing - REST service, UI app, cli app, DB, etc.
● Examples
○ Unit testing
○ Non-unit testing

4. CI = Continuous Integration
● “is the practice of automating the integration of code changes from multiple
contributors into a single software project”
● “CI process is comprised of automatic tools that assert the new code’s
correctness before integration.”
● Tools - version control system, automated code quality tests, syntax style
review tools, and more.
Atlassian: What is CI

5. Test Phases
source

6. Test Phases
4 phase test at xunitpatterns.com

7. Test Phases explained
source

8. Test Suite
● Contains test cases
● Contains test suites
(composite)
● Demo

9. Test Suite - test case organization
● Per feature - user login
● Per fixture - test cases need a shopping basket with 2
items inside.

10. Smells

11. Smells
● Definition
● What can you do ?
5 Whys

12. ● Code smells
● Behavior smells
● Project smells
Types of Smells

13. Project Smells

14. Behavior Smells
● API/UI sensitivity
● Context/Data sensitivity - Fixture’s modified.
● Behavior sensitivity - SUT’s modified.

15. Code Smells
● Obscure tests
● Conditional test logic
● Hard-coded test data literals
● Hard-to-test code
● Code duplication
● Test logic in production

16. ● 4 test phases
● Tests’ organization
● Smells
Wrap-up

17. Review
Questions?
Answers.