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
My own preferred testing techniques
Search
Sponsored
·
Ship Features Fearlessly
Turn features on and off without deploys. Used by thousands of Ruby developers.
→
dgageot
September 26, 2011
Programming
1
120
My own preferred testing techniques
dgageot
September 26, 2011
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
810
CodeStory 2013 "La Selection Finale"
dgageot
0
770
Let's make this test suite run faster! - BeJUG
dgageot
1
580
Finale Code Story
dgageot
1
720
Le facilitateur, un rôle encore méconnu
dgageot
1
200
Mockito. Ecrire des tests unitaires est devenu simple.
dgageot
2
440
Git, la gestion de configuration qui vous veut du bien
dgageot
1
470
Let's make this test suite run faster
dgageot
1
72
Other Decks in Programming
See All in Programming
テレメトリーシグナルが導くパフォーマンス最適化 / Performance Optimization Driven by Telemetry Signals
seike460
PRO
2
140
Reactive ❤️ Loom: A Forbidden Love Story
franz1981
2
140
S3ストレージクラスの「見える」「ある」「使える」は全部違う ─ 体験から見た、仕様の深淵を覗く
ya_ma23
0
920
今からFlash開発できるわけないじゃん、ムリムリ! (※ムリじゃなかった!?)
arkw
0
140
[SF Ruby Feb'26] The Silicon Heel
palkan
0
120
Takumiから考えるSecurity_Maturity_Model.pdf
gessy0129
1
150
Symfony + NelmioApiDocBundle を使った スキーマ駆動開発 / Schema Driven Development with NelmioApiDocBundle
okashoi
0
210
Vuetify 3 → 4 何が変わった?差分と移行ポイント10分まとめ
koukimiura
0
180
コーディングルールの鮮度を保ちたい / keep-fresh-go-internal-conventions
handlename
0
230
メッセージングを利用して時間的結合を分離しよう #phperkaigi
kajitack
3
300
new(1.26) ← これすき / kamakura.go #8
utgwkk
0
2.6k
安いハードウェアでVulkan
fadis
1
750
Featured
See All Featured
Bootstrapping a Software Product
garrettdimon
PRO
307
120k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
333
22k
Public Speaking Without Barfing On Your Shoes - THAT 2023
reverentgeek
1
340
Principles of Awesome APIs and How to Build Them.
keavy
128
17k
What’s in a name? Adding method to the madness
productmarketing
PRO
24
4k
How to Talk to Developers About Accessibility
jct
2
160
Neural Spatial Audio Processing for Sound Field Analysis and Control
skoyamalab
0
230
The Impact of AI in SEO - AI Overviews June 2024 Edition
aleyda
5
770
Raft: Consensus for Rubyists
vanstee
141
7.4k
RailsConf 2023
tenderlove
30
1.4k
Navigating Team Friction
lara
192
16k
Crafting Experiences
bethany
1
93
Transcript
My own preferred testing techniques Paris Java User Group
www.parisjug.org Copyright(c) 2010 Paris JUG, Licence CC-Creatives Commons 2.0 France
- Paternité - Pas d’utilisation commerciale - Partage des Conditions à l’identique
Frameworks My own preferred testing techniques JUnit 4+ More expressive
tests More robust Faster Plugins
Personal taste only
Plugins
MoreUnit, a unit test friendly Eclipse http://moreunit.sourceforge.net/ See what’s tested
MoreUnit http://moreunit.sourceforge.net/ Jump to Test
MoreUnit http://moreunit.sourceforge.net/ Run current test Refactoring friendly (move, rename, delete)
http://moreunit.sourceforge.net/ Demo
Continuous testing Runs all impacted tests after each code change
Eclipse and Intellij OpenSource, Free http://infinitest.org
Demo
Continuous testing JUnit Max Runs all impacted tests after each
code change Try to run tests failing most often, first Eclipse and Intellij OpenSource, Free Developed by Kent Beck http://www.junitmax.com/
Frameworks
Hamcrest More readable assertions
Hamcrest More samples + easy to write custom matchers
So
FEST-Assert More readable assertions Demo
FEST-Assert More readable assertions OpenSource http://fest.easytesting.org/
JUnit 4.8.2 Worst logo ever!
Do you known/use all the features? @Test @Before, @After, @BeforeClass,
@AfterClass @RunWith @Theory, @DataPoint(s) @Rule @SuiteClasses @Category (beta) JUnit 4.8.2 Demo
@Categories and @SuiteClasses JUnit 4.8.2
@Categories and @SuiteClasses JUnit 4.8.2
@Categories and @SuiteClasses JUnit 4.8.2 Cumbersome Need not forget to
add each test manually in all suites Who doesn’t run all the tests every build? :-)
@Rule Take a look at the code of MethodRule, ExternalResource,
TestWatchman, Verifier... Write your own rules if they make the tests easier to read. JUnit 4.8.2
Thank you Q/A
www.parisjug.org Copyright(c) 2010 Paris JUG, Licence CC-Creatives Commons 2.0 France
- Paternité - Pas d’utilisation commerciale - Partage des Conditions à l’identique