Slide 1
Slide 1 text
https://maritvandijk.com/
@MaritvanDijk77
github.com/mlvandijk
@[email protected]
Use Testing to
Develop Better
Software Faster
OOP 2023 DIGITAL - Feb 9th, 2023
Slide 2
Slide 2 text
Some tests…
@MaritvanDijk77
Slide 3
Slide 3 text
@MaritvanDijk77
Slide 4
Slide 4 text
@MaritvanDijk77
Slide 5
Slide 5 text
Build quality in
@MaritvanDijk77
Slide 6
Slide 6 text
https://danashby.co.uk/2016/10/19/continuous-testing-in-devops/ @MaritvanDijk77
Slide 7
Slide 7 text
https://janetgregory.ca/testing-from-a-holistic-point-of-view/
@MaritvanDijk77
Slide 8
Slide 8 text
@MaritvanDijk77
Slide 9
Slide 9 text
The right
feedback
at the
right time
@MaritvanDijk77
Slide 10
Slide 10 text
Ask questions
@MaritvanDijk77
Slide 11
Slide 11 text
@MaritvanDijk77
Slide 12
Slide 12 text
@MaritvanDijk77
Slide 13
Slide 13 text
https://elizabethzagroba.com/posts/2019/2019-01-25_have-i-tried-enough-weird-stuff/
@ezagroba
@MaritvanDijk77
Slide 14
Slide 14 text
@MaritvanDijk77
Slide 15
Slide 15 text
https://github.com/minimaxir/big-list-of-naughty-strings
@MaritvanDijk77
Slide 16
Slide 16 text
https://twitter.com/sempf/status/514473420277694465?s=20&t=ZDqpc0arpJZeUBL6M1J3jg
https://www.sempf.net/post/On-Testing1
@MaritvanDijk77
Slide 17
Slide 17 text
How are we going to test this?
@MaritvanDijk77
Slide 18
Slide 18 text
Test pyramid
@MaritvanDijk77
https://martinfowler.com/bliki/TestPyramid.html
Slide 19
Slide 19 text
@MaritvanDijk77
Slide 20
Slide 20 text
Build testability in
@MaritvanDijk77
Slide 21
Slide 21 text
@MaritvanDijk77
Slide 22
Slide 22 text
“When developers are involved in creating and maintaining
acceptance tests:
1. code becomes more testable (this is why TDD is
important)
2. they will care more and invest more effort into
maintaining & fixing them.”
- Accelerate by Nicole Forsgren, PhD
Jez Humble, and Gene Kim
Slide 23
Slide 23 text
Use the right tools
@MaritvanDijk77
Slide 24
Slide 24 text
@MaritvanDijk77
Slide 25
Slide 25 text
Use tools as intended
@MaritvanDijk77
Slide 26
Slide 26 text
Tests should increase confidence
@MaritvanDijk77
Slide 27
Slide 27 text
@MaritvanDijk77
Slide 28
Slide 28 text
Tests should be reliable
@MaritvanDijk77
Slide 29
Slide 29 text
@MaritvanDijk77
Slide 30
Slide 30 text
@MaritvanDijk77
Slide 31
Slide 31 text
@MaritvanDijk77
https://www.youtube.com/watch?v=1cZRBtrvys0
Slide 32
Slide 32 text
Run your tests
@MaritvanDijk77
Slide 33
Slide 33 text
Run your tests
@MaritvanDijk77
Slide 34
Slide 34 text
Never
trust a test
you haven’t
seen fail
@MaritvanDijk77
Slide 35
Slide 35 text
@MaritvanDijk77
Slide 36
Slide 36 text
A failing test should tell you
exactly what’s wrong quickly
@MaritvanDijk77
Slide 37
Slide 37 text
@MaritvanDijk77
@MaritvanDijk77
Kevlin Henney
GOTO 2022 Amsterdam
Slide 38
Slide 38 text
Use
meaningful,
descriptive
names
@MaritvanDijk77
Slide 39
Slide 39 text
Each test should test one thing
@MaritvanDijk77
Slide 40
Slide 40 text
@MaritvanDijk77
Readability of your tests
Slide 41
Slide 41 text
@MaritvanDijk77
Slide 42
Slide 42 text
@MaritvanDijk77
Slide 43
Slide 43 text
TL; DR: Test your code!
@MaritvanDijk77
https://www.redbubble.com/people/hogfish (Trish Khoo @hogfish)
Slide 44
Slide 44 text
https://maritvandijk.com/
@MaritvanDijk77
github.com/mlvandijk
@[email protected]
Slides & More
https://maritvandijk.com/presentations/better-software-faster/