My own preferred testing
techniques
Paris Java User Group
Slide 2
Slide 2 text
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
Slide 3
Slide 3 text
Frameworks
My own preferred testing techniques
JUnit 4+
More expressive tests
More robust
Faster
Plugins
Slide 4
Slide 4 text
Personal taste only
Slide 5
Slide 5 text
Plugins
Slide 6
Slide 6 text
MoreUnit, a unit test friendly Eclipse
http://moreunit.sourceforge.net/
See what’s tested
Slide 7
Slide 7 text
MoreUnit
http://moreunit.sourceforge.net/
Jump to Test
Slide 8
Slide 8 text
MoreUnit
http://moreunit.sourceforge.net/
Run current test
Refactoring friendly
(move, rename, delete)
http://moreunit.sourceforge.net/
Demo
Slide 9
Slide 9 text
Continuous testing
Runs all impacted tests after each code change
Eclipse and Intellij
OpenSource, Free
http://infinitest.org
Slide 10
Slide 10 text
Demo
Slide 11
Slide 11 text
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/
Slide 12
Slide 12 text
Frameworks
Slide 13
Slide 13 text
Hamcrest
More readable assertions
Slide 14
Slide 14 text
Hamcrest
More samples
+ easy to write custom matchers
Slide 15
Slide 15 text
So
Slide 16
Slide 16 text
FEST-Assert
More readable assertions
Demo
Slide 17
Slide 17 text
FEST-Assert
More readable assertions
OpenSource
http://fest.easytesting.org/
Slide 18
Slide 18 text
JUnit 4.8.2
Worst logo
ever!
Slide 19
Slide 19 text
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
Slide 20
Slide 20 text
@Categories and @SuiteClasses
JUnit 4.8.2
Slide 21
Slide 21 text
@Categories and @SuiteClasses
JUnit 4.8.2
Slide 22
Slide 22 text
@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? :-)
Slide 23
Slide 23 text
@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
Slide 24
Slide 24 text
Thank you
Q/A
Slide 25
Slide 25 text
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