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
Let's make this test suite run faster! - BeJUG
Search
dgageot
April 05, 2012
Programming
1
560
Let's make this test suite run faster! - BeJUG
dgageot
April 05, 2012
Tweet
Share
More Decks by dgageot
See All by dgageot
Docker on Google Cloud Platform
dgageot
0
1.7k
Lightning Talk Mix-IT 2014
dgageot
0
800
CodeStory 2013 "La Selection Finale"
dgageot
0
750
Finale Code Story
dgageot
1
710
Le facilitateur, un rôle encore méconnu
dgageot
1
200
Mockito. Ecrire des tests unitaires est devenu simple.
dgageot
2
430
Git, la gestion de configuration qui vous veut du bien
dgageot
1
460
My own preferred testing techniques
dgageot
1
110
Let's make this test suite run faster
dgageot
1
58
Other Decks in Programming
See All in Programming
kiroでゲームを作ってみた
iriikeita
0
140
PHPUnitの限界をPlaywrightで補完するテストアプローチ
yuzneri
0
380
実践 Dev Containers × Claude Code
touyu
1
140
Understanding Kotlin Multiplatform
l2hyunwoo
0
250
Quality Gates in the Age of Agentic Coding
helmedeiros
PRO
1
120
新世界の理解
koriym
0
130
Strands Agents で実現する名刺解析アーキテクチャ
omiya0555
1
110
一人でAIプロダクトを作るための工夫 〜技術選定・開発プロセス編〜 / I want AI to work harder
rkaga
4
480
「次に何を学べばいいか分からない」あなたへ──若手エンジニアのための学習地図
panda_program
3
710
ワープロって実は計算機で
pepepper
2
920
DMMを支える決済基盤の技術的負債にどう立ち向かうか / Addressing Technical Debt in Payment Infrastructure
yoshiyoshifujii
5
760
バイブコーディング超えてバイブデプロイ〜CloudflareMCPで実現する、未来のアプリケーションデリバリー〜
azukiazusa1
3
790
Featured
See All Featured
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
110
19k
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
53
2.9k
Designing for Performance
lara
610
69k
Side Projects
sachag
455
43k
GitHub's CSS Performance
jonrohan
1031
460k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
30
2.2k
Done Done
chrislema
185
16k
Code Review Best Practice
trishagee
69
19k
What’s in a name? Adding method to the madness
productmarketing
PRO
23
3.6k
BBQ
matthewcrist
89
9.8k
Principles of Awesome APIs and How to Build Them.
keavy
126
17k
Docker and Python
trallard
45
3.5k
Transcript
Let's make this test suite run faster!
David Gageot Freelance developer @dgageot javabien.net
Why make a test suite run faster?
“ I firmly believe it can make your product better.
Faster to test leads to faster to write, deploy and use ” Anonymous bearded freelance developper
You test early and often. Right?
Continuous integration?
Continuous testing?
Continuous deployment?
Testing a lot can lead to waiting a lot
How wants his coding room to look like
Test suite duration can be contained
Jenkins slaves to the rescue
Jenkins slaves to the rescue. not.
Why complicated when it can be simple?
I’ll share a few easy tricks
“ I firmly believe it can make your product better.
Faster to test leads to faster to write, deploy and use ” Anonymous bearded freelance developper
How can we accelerate the tests? The Cheater The Lazy
The Cheater
Buy a faster machine. Tests are cpu/
Thank you Q/A
BUT single threaded tests get slower 0 25 50 75
100 2007 2008 2009 2010
Use all the cores with Maven3 mvn -T1 clean install
: 5:05s mvn -T4 clean install : 3:10s Beware of tests with side effects
It’s not just me
Use all the cores with JUnit/TestNG Beware of tests with
side effects
That’s it for cheaters No silver bullet
The Lazy
Delete useless tests It’s so simple, we don’t do it...
Even better, delete dead code
Even better, delete dead code Leads to deleting even more
useless tests
Work in a sandbox In-memory database H2 behaves much like
MySql As simple as changing an xml file The database is slow
It’s Not only SQL If going for NoSQL, choose a
server that can run in-process eg. Voldemort The network is slow
In-memory SMTP Server SubEtha SMTP
Abstract the filesystem Apache VFS (Virtual File System) Spring Resource...
In-memory everything As a bonus, tests will run smoother
Of course all of these are easier to setup at
the beginning of a project
The
5 minutes a day can make a difference
Don’t test business rules in integration Unit tests are often
a better place
Not the same scale of speed 10sec .01sec
Action #1 - Break the longer integration Into one faster
integration test and a lot of small
Action #2 - Mock the slowest layers Mocks are not
just for unit tests eg. with Spring and Mockito spies
Action #3 - Don’t test through the Selenium is often
overkill «But my application is complex!» «My users want complex features, My users want Ajax» «I need to test browser compatibility!»
Really?
Complexity has a cost That you pay each time tests
run
Test through the browser the strict Unit test Javascript
Action #4 - Sometimes be old school write (easier to
test) server-side code
Thank you Q/A
One more thing™ Action #0 - Simplify and optimize your
code Tests will run faster Keep that one secret...
Thank you Q/A