Distributed testing on Rails

Transcript

1. DR. KOWALSKI OR: HOW I LEARNED TO STOP WAITING AND LOVED THE TESTS
2. skroutz.gr
3. 37,640 LINES OF CODE
4. 8,414 SPEC EXAMPLES 1:1.4 CODE TO TEST RATIO
5. 28 MINUTES TO RUN (ORIGINALLY)
6. 16 DEVELOPERS ALL WANTING TO DEPLOY SOMETHING
7. 5-25 DEPLOYS PER DAY EACH ONE HAS TO BE TESTED
8. PARTIAL TESTING NOT A SOLUTION
9. THE "PLAN"
10. DISTRIBUTED TESTING PARTLY CUSTOM
11. FAST TEST RESULTS LESS THAN 5 MINUTES
12. USE OUR HARDWARE PIGGYBACK ON DEVELOPER MACHINES
13. WHY CUSTOM? WHY NOT?
14. FOR UNIQUENESS YOU ARE A PRETTY LITTLE SNOWFLAKE
15. FOR UNIQUENESS YOU ARE A PRETTY LITTLE SNOWFLAKE •Databases (MySQL, MongoDB, etc) •External services (Elastic) •Intelligently distribute specs to Hydras •Nothing works “out of the box” •We don’t want VMs into our developer machines
16. FOR GREAT SPEED FROM 28 MINUTES TO 4 AND A HALF
17. FOR GREAT SPEED FROM 28 MINUTES TO 4 AND A HALF Workers Time Speed (ex/min) 1 28:37 294 2 17:03 493 3 12:07 694 4 10:18 817 5 8:51 951 6 7:24 1,137 7 6:24 1,314 8 5:46 1,460 9 5:23 1,565 10 4:59 1,688 11 4:40 1,803
18. FOR GREAT SPEED FROM 28 MINUTES TO 4 AND A HALF 0 7.5 15 22.5 30 1 2 3 4 5 6 7 8 9 10 11 0 500 1,000 1,500 2,000 Time in minutes Examples per minute Time Speed
19. FOR HINDSIGHT WEEKS OF TEST RESULTS AVAILABLE FOR REVIEW
20. FOR HINDSIGHT WEEKS OF TEST RESULTS AVAILABLE FOR REVIEW •We are approaching 5,000 builds of the master branch •Identify “Heisenspecs” •Generate statistics
21. FOR FUN! DISTRIBUTED PROCESSING IS A BITCH
22. FOR FUN! DISTRIBUTED PROCESSING IS A BITCH •Yes, we do love a challenge
23. HOW? THE MAIN COMPONENTS
24. WHO IS JENKINS? KNOWS WHAT WENT BAD, COMPLAINS CONSTANTLY
25. WHO IS JENKINS? KNOWS WHAT WENT BAD, COMPLAINS CONSTANTLY •Java web application •Monitors git for changes •Keeps track of builds •Can’t do proper distributed testing •Fires up Kowalski
26. WHO IS KOWALSKI? BEHIND THE SCENES, GIVES COMMANDS
27. WHO IS KOWALSKI? BEHIND THE SCENES, GIVES COMMANDS •Splits spec files into chunks •Feeds them to the Hydras •Gathers the output •Reports to Jenkins
28. WHO IS THE HYDRA? "DEMOCRATIZES" YOUR RESOURCES
29. WHO IS THE HYDRA? "DEMOCRATIZES" YOUR RESOURCES •A user in each developer’s machine •Local binaries for services (SQL, MongoDB, Elastic etc) •Reports to Kowalski •Limited to 1 CPU core
30. BITS & PIECES COMPLETING THE IMAGE
31. GITLAB INTEGRATION WHICH GIT COMMITS FAILED THE BUILD?
32. WALL DISPLAY WHAT'S GOING ON RIGHT NOW?
33. TMPFS/RAMFS THE SOLIDEST OF STATE FOR YOUR HDD
34. PERSONAL BUILDS EVERYONE CAN ORDER A BUILD OF THEIR OWN