Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Building a testing culture
Search
Pedro Tavares
May 10, 2018
Programming
0
1.1k
Building a testing culture
Pedro Tavares
May 10, 2018
Tweet
Share
More Decks by Pedro Tavares
See All by Pedro Tavares
Diving into Merkle Trees
ordepdev
1
450
Harvest, Yield, and Scalable Tolerant Systems
ordepdev
0
160
Things you should know about Database Storage and Retrieval
ordepdev
0
120
Building a testing culture
ordepdev
0
140
Things you should know about Database Storage and Retrieval
ordepdev
0
1.4k
GitLab as an Application Lifecycle Management Suite
ordepdev
0
280
Consumer Driven Contracts
ordepdev
0
1.2k
Optional<Java>
ordepdev
0
1.2k
Microservices? You have to
ordepdev
0
1.1k
Other Decks in Programming
See All in Programming
フロントエンドの現在地とこれから
koba04
10
4.7k
GrafanaのHTTP API を眺めてみよう
rinchoku
0
460
Kotlin Multiplatform at Stable and Beyond (Kotlin Vienna, October 2024)
zsmb
2
410
Micro Frontends for Java Microservices - dev2next 2024
mraible
PRO
0
230
UnJSで簡単に始めるCLIツール開発 / cli-tool-development-with-unjs
aoseyuu
2
380
ポケモンで考えるコミュニケーション / Communication Lessons from Pokémon
mackey0225
5
220
Vaporモードを大規模サービスに最速導入して学びを共有する
kazukishimamoto
3
1.1k
Honoの来た道とこれから
yusukebe
6
870
Golang と Erlang
taiyow
7
1.7k
知られざるNaNの世界
hole
3
1.1k
How to debug Xdebug... or any other weird bug in PHP
dunglas
2
1.5k
Jakarta EE as Seen Trough the Lens of the ASF
ivargrimstad
0
800
Featured
See All Featured
Designing the Hi-DPI Web
ddemaree
280
34k
A designer walks into a library…
pauljervisheath
202
24k
The Cult of Friendly URLs
andyhume
77
6k
Writing Fast Ruby
sferik
626
60k
Happy Clients
brianwarren
97
6.7k
Building Applications with DynamoDB
mza
90
6k
The Invisible Side of Design
smashingmag
297
50k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
43
6.6k
Mobile First: as difficult as doing things right
swwweet
222
8.9k
Docker and Python
trallard
40
3k
Teambox: Starting and Learning
jrom
132
8.7k
Ruby is Unlike a Banana
tanoku
96
11k
Transcript
TESTING building CULTURE
None
THIS IS NOT ABOUT TDD!
@ordepdev
First of all Why testing?
“It’s time for software developers to take up the mantle
of responsibility for what they produce.
Testing is the engineering rigour of software development.
Responsibility — the state or fact of being accountable or
to blame for something.
Rigour — the quality of being extremely thorough and careful.
Software Engineering
An engineering discipline that is concerned with all aspects of
software production.
MUCH MORE THAN CODING!
Types of Bad Software Projects
1. Without tests.
Zero Automated Tests.
ZERO!
Lack of professionalism?
Lack of skills?
Lack of knowledge?
Lack of time to test?
It can be all of them.
What about software quality?
Relax, they test all features with manual testing.
None
2. With Wrongly Designed Tests..
Testing is HARD.
None
Testing pitfalls: coupling.
Implementation Boundary Testing Boundary
Implementation Boundary Testing Boundary ✅ ✅ ✅ ✅ ✅ ✅
✅ ✅ ❌ ❌
Uncertainty and Doubt.
Implementation Boundary Testing Boundary ✅ ✅ ✅ ✅ ✅ ❌
❌ ❌ ❌ ❌
Testing pitfalls: performance.
Taking too much time? — that’s a no run.
Types of Testing
1. Testing after the implementation.
2. Testing during the implementation.
3. Testing that reproduce bugs.
It’s our job to build a testing culture!
But how?
5 rules.
1. Every change must have tests.
50 100 150 200 Development Unit Tests Functional Tests System
Tests Production The cost of bugs
Bugs in production are embarrassing and costly.
2. Write more than unit tests.
Mutation testing!
def add(x,y) x + y end def add(x,y) x -
y end Source Code Mutation
Property-based testing!
http://blog.jessitron.com/2013/04/property-based-testing-what-is-it.html
Contract testing!
None
Model-based testing!
Try formal methods! https://www.infoq.com/presentations/aws-testing-tla
3. Bug fixing must have tests.
Don’t repeat the same bug hunting — write a test!
4. Testing code must be reviewed.
A well-designed test suite is much easier to read, understand
and evolve.
Testing code is production code!
5. Test suites must be consistent.
L12. assertEquals(input, expectation); L35. assertEquals(expectation, input); L43. assertThat(input).isEqualTo( expectation); Assertions
L12. assertEquals(input, expectation); L35. assertEquals(expectation, input); L43. assertThat(input).isEqualTo( expectation); Assertions
L12. createEntity L35. create_withValidPayload_success L43. create_withValidPayload_shouldPersistEntity Test Methods
L12. createEntity L35. create_withValidPayload_success L43. create_withValidPayload_shouldPersistEntity Test Methods
We must share the same values, practices, and tools.
Enforce them through code reviews, static analysis, and style checking
tools.
Wrapping up.
“People who are successful at automating tasks tend to work
this way in every aspect of their jobs. It is just how they work; it is part of their culture.”
Manual work is a bug. acmqueue | january-february 2018
ALWAYS BE AUTOMATING!
GO AND FIX YOUR BROKEN CULTURE!
TESTING building CULTURE