Let's make this test suite run faster - Paris JUG 2011
•
0 likes•560 views
The document discusses ways to make test suites run faster. It suggests distributing tests across multiple servers, running tests in parallel by using all CPU cores, deleting redundant and dead code to remove unnecessary tests, running tests in memory without accessing the network or file system, and mocking slow layers to isolate tests. Simplifying code is also recommended so that tests can run more quickly.
Recommended
More Related Content
What's hot
What's hot (11)
Viewers also liked
Similar to Let's make this test suite run faster - Paris JUG 2011
Similar to Let's make this test suite run faster - Paris JUG 2011 (20)
Recently uploaded
Recently uploaded (20)
Let's make this test suite run faster - Paris JUG 2011
- 1. Let's make this test suite run faster! Paris Java User Group
- 2. 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
- 3. Let's make this test suite run faster! Why? What for ? http://farm1.static.flickr.com/158/349497988_fb751a5e3a_z.jpg
- 4. You test early and often Don’t you? http://farm1.static.flickr.com/97/246816211_573c2901e1_z.jpg?zz=1
- 5. Continuous integration, continuous testing... ...even continuous deployment http://vator.tv/images/attachments/150609195630ctd.gif
- 6. Testing often Often means waiting a lot http://farm3.static.flickr.com/2505/3772118924_11fe195ef1.jpg
- 7. Your coding room doesn’t have to look like this What for ? http://upload.wikimedia.org/wikipedia/commons/3/3f/ Nespresso_boutique.JPG
- 8. Tests can be fast Even if lines of code keep growing
- 9. Easy! Let’s distribute across multiple hudson servers
- 10. It doesn’t have to be complicated I’ll share a few simple tricks
- 11. It can make your product better Simple to test, means simple to write, deploy and USE Photo: http://www.flickr.com/photos/zoutedrop/2317065892/
- 12. How can we accelerate the tests? The Cheater The Lazy The Brave http://all-the-movies.cowblog.fr/images/arton1122.jpg
- 13. The Cheater The Lazy The Brave http://all-the-movies.cowblog.fr/images/arton1122.jpg
- 14. Buy a faster machine Tests are cpu/memory bound http://farm1.static.flickr.com/28/93569705_1c562b413a_z.jpg?zz=1
- 15. Be warned Single threaded tests get slower over time 100 75 50 25 0 2007 2008 2009 2010 http://farm5.static.flickr.com/4096/4819945812_735744e0fc_z.jpg
- 16. Use all the cores parallel build with maven3 mvn -T1 clean install : 5:05s mvn -T4 clean install : 3:10s
- 17. Use all the cores parallel build with maven3
- 18. Use all the cores Surefire 2.7.1 For JUnit/TestNG tests .
- 19. The Cheater The Lazy The Brave http://all-the-movies.cowblog.fr/images/arton1122.jpg
- 20. Delete redundant tests It’s so simple, we don’t do it... http://geekandpoke.typepad.com/geekandpoke/images/2008/04/24/ turingtest.jpg
- 21. Even better, delete dead code To delete yet other useless tests http://farm1.static.flickr.com/58/191393602_3d9b643ab0_z.jpg
- 22. Work in a sandbox The network is too slow In-memory database: H2 Behaves more like MySql than Hsqldb
- 23. It’s Not only SQL If going with NoSQL, take a server that can run in-process eg. Voldemort
- 24. In-memory SMTP Server SubEtha SMTP
- 25. Everything local and in-memory Files Apache VFS (Virtual File System) Spring Resource... As a bonus, tests will run smoother .
- 26. The Cheater The Lazy The Brave http://all-the-movies.cowblog.fr/images/arton1122.jpg
- 27. Don’t test business rules in integration tests Unit tests is often a better place http://upload.wikimedia.org/wikipedia/commons/b/bd/ Contortionist_Ravi_standing.jpg
- 28. Don’t test business rules in integration tests Unit tests is often a better place Functional test (on a web page) 10s Unit test 0.01s
- 29. Take the longer integration test Break it in one faster integration test and a lot of small unit tests http://farm2.static.flickr.com/1168/3166709586_96f9a3fd95.jpg
- 30. Or mock the slowest layers eg. functional test with Spring and Mockito Mocks are not just for unit tests
- 31. Don’t test through the browser Selenium is often overkill «But my application is complex!» «My users want complex features, My users want Ajax» «I need to test browser compatibility!» Photo: http://www.flickr.com/photos/zoutedrop/2317065892/
- 32. Really ? http://i.zdnet.com/blogs/complexity-and-false-hope.jpg
- 33. Complexity has a cost That you pay each time a test runs http://thehongkongfixereng.files.wordpress.com/2008/07/couteau-suisse.jpg
- 34. Test through the browser the strict minimal Use javascript unit tests for the rest http://farm2.static.flickr.com/1168/3166709586_96f9a3fd95.jpg
- 35. I tend to be old school And write server-side code most of the time http://www.celebridiot.com/wp-content/uploads/2009/06/ rick_astley_death_hoax.jpg
- 36. One more thing... Simplify and optimize your code Tests will run faster .
- 37. Thank you Q/A
- 38. 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