From 2 Hours to 7 Minutes with Distributed Testing

Over the last 8 years, the Rails application that we work on has steadily grown, and the test suite has grown with it. Today, our tests take 2 hours to run on a single machine. We run all of these tests as part of our integration process...in under 7 minutes. We developed a distributed test framework, Gorgon, to achieve this. In this presentation, I show why you should run all your tests as part of your integration process and how we achieve this with Gorgon.

Transcript

1. From 2 Hours to 7 Minutes with Distributed Testing Arturo Pie @arturo_pie
2. From 2 Hours to 7 Minutes with Distributed Testing Arturo Pie @arturo_pie
4. Long test feedback loop causes pain
5. Agenda Why a long test feedback loop causes pain? How we made test feedback loop short at Nulogy
6. Agenda Why a long test feedback loop causes pain? How we made test feedback loop short at Nulogy
7. Very Small Test Suite
8. Synchronous Integration
9. 5-minute Test Suite
10. Integration Token
11. RIP Pacman
12. Richard
13. 2-hour Test Suite
14. Asynchronous Integration
15. What now?
16. Better < 10
17. Key Takeaway Prefer synchronous over asynchronous integration
18. Continuous Integration Section
19. Agenda Why a long test feedback loop causes pain? How we made test feedback loop short at Nulogy
21. 7 years old > 1.8k classes > 20k tests 2 hours to run tests 19 developers
22. Gorgon
23. Maybe a video of this in here?
26. If you want to try it … ◻️ Train Users ◻️ Setup components (RabbitMQ, File Server, Listeners) ◻️ Configure your project (remote_test Rails environment) ◻️ Customize Gorgon run (callbacks)
27. For Gorgon Users
28. Network Your Host Remote Host 1 Remote Host N
29. Idle state Your Host Remote Host 1 Remote Host N AMQP
30. gorgon_listener.json
31. Run Gorgon Your Host Remote Host 1 Remote Host N AMQP
32. Push Project & Job Your Host Remote Host 1 Remote Host N rsync AMQP AMQP
33. gorgon.json
34. gorgon.json
35. gorgon.json
36. gorgon.json
37. Push Project & Job Your Host Remote Host 1 Remote Host N AMQP AMQP
38. Pull project Your Host Remote Host 1 Remote Host N AMQP rsync
39. after_sync callback Remote Host x
40. gorgon.json
41. after_sync callback
42. Fork Worker Manager Remote Host x
43. before_creating_workers
44. Fork Workers Remote Host x
45. gorgon_listener.json
46. Workers Remote Host x
47. before_start callback
48. database.yml
49. Gemfile
50. environments/remote_test.rb
51. Workers Remote Host x
52. Done Remote Host x
53. Done Remote Host x
54. Done Remote Host x
55. Back to Listening Your Host Remote Host 1 Remote Host N AMQP
56. For Gorgon Administrators ☑️ Train Users ☑️ Setup components (RabbitMQ, File Server, Listeners) ☑️ Configure your project (remote_test Rails environment) ☑️ Customize Gorgon run (callbacks)
57. I hope you learned … Why a long test feedback loop causes pain? How we made test feedback loop short at Nulogy
58. Thank you
59. Q & A Project: https://github.com/nulogy/Gorgon/ My github account: https://github.com/arturopie Twitter: @arturo_pie