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
June 02, 2018
Programming
0
150
Building a testing culture
Pedro Tavares
June 02, 2018
Tweet
Share
More Decks by Pedro Tavares
See All by Pedro Tavares
Diving into Merkle Trees
ordepdev
1
600
Harvest, Yield, and Scalable Tolerant Systems
ordepdev
0
180
Things you should know about Database Storage and Retrieval
ordepdev
0
140
Building a testing culture
ordepdev
0
1.3k
Things you should know about Database Storage and Retrieval
ordepdev
0
1.5k
GitLab as an Application Lifecycle Management Suite
ordepdev
0
360
Consumer Driven Contracts
ordepdev
0
1.4k
Optional<Java>
ordepdev
0
1.3k
Microservices? You have to
ordepdev
0
1.2k
Other Decks in Programming
See All in Programming
Passkeys for Java Developers
ynojima
2
760
Prism.parseで 300本以上あるエンドポイントに 接続できる権限の一覧表を作ってみた
hatsu38
1
100
Effect の双対、Coeffect
yukikurage
2
280
型付け力を強化するための Hoogle のすゝめ / Boosting Your Type Mastery with Hoogle
guvalif
1
250
Enterprise Web App. Development (2): Version Control Tool Training Ver. 5.1
knakagawa
1
110
【TSkaigi 2025】これは型破り?型安全? 真実はいつもひとつ!(じゃないかもしれない)TypeScript クイズ〜〜〜〜!!!!!
kimitashoichi
1
300
Development of an App for Intuitive AI Learning - Blockly Summit 2025
teba_eleven
0
100
実践ArchUnit ~実例による検証パターンの紹介~
ogiwarat
1
200
統一感のある Go コードを生成 AI の力で手にいれる
otakakot
0
770
人には人それぞれのサービス層がある
shimabox
3
630
OpenNext + Hono on Cloudflare でイマドキWeb開発スタックを実現する
rokuosan
0
110
ts-morph実践:型を利用するcodemodのテクニック
ypresto
1
580
Featured
See All Featured
Git: the NoSQL Database
bkeepers
PRO
430
65k
Put a Button on it: Removing Barriers to Going Fast.
kastner
60
3.9k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
45
9.6k
It's Worth the Effort
3n
184
28k
Docker and Python
trallard
44
3.4k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
367
26k
Producing Creativity
orderedlist
PRO
346
40k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
29
2.6k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
47
2.8k
Large-scale JavaScript Application Architecture
addyosmani
512
110k
We Have a Design System, Now What?
morganepeng
52
7.6k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
130
19k
Transcript
TESTING building CULTURE
https://ordepdev.me/posts/test-driven-developers
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, we test all features with manual testing.
None
2. With Wrongly Designed Tests..
Testing is HARD.
https://twitter.com/codepipes/status/987934900111138816
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.
https://twitter.com/pwlporto/status/999258562370170880
We do not know how much an increase in coverage
can decrease the number of defects.” “
https://ordepdev.me/posts/code-coverage
Mutation testing!
def add(x,y) x + y end def add(x,y) x -
y end Source Code Mutation
Property-based testing! https://hypothesis.works/articles/quickcheck-in-every-language
http://blog.jessitron.com/2013/04/property-based-testing-what-is-it.html
Contract testing! https://martinfowler.com/bliki/ContractTest.html
https://ordepdev.me/posts/boost-your-confidence-with-consumer-driven-contracts
Model-based testing! http://mit.bme.hu/~micskeiz/pages/modelbased_testing.html
Instead of writing hundreds of test cases, write an abstract
model of the system and generate a set of test cases.” “
None
Formal methods! https://www.infoq.com/presentations/aws-testing-tla
Formal methods use mathematical proof as a complement to system
testing in order to ensure correct behavior.” “
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.
5+1.Test suites must be visible.
A failed test is a failed build!
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 @ordepdev ordepdev.me Thanks!