A Monolith for Hundreds of Client Versions: How We Write and Maintain Tests

on YouTube ↗52m

" summary

Badoo engineers describe their testing practice for a large monolithic backend that must support hundreds of client versions. They explain their development flow and why developers write their own tests, giving concrete metrics (about 100,000 unit tests and 20,000 integration tests) and discussing how that practice affects responsibility and maintenance.

AI-written summary · about

" chapters (18)

1. 0:00Introduction
2. 1:10Development and testing process
3. 4:40Unit tests and specifics
4. 7:30Legacy code problems and SoftMocks
5. 8:53Mutation testing and test quality
6. 11:03Integration tests and databases
7. 13:29Max tests for DB isolation
8. 15:36API tests and client emulation
9. 17:21Test user pool
10. 20:59Test hooks and backdoors
11. 24:14Security and test data protection
12. 24:57SoftMocks and localization
13. 28:29API test issues and rules
14. 31:20Test execution setup
15. 34:51Parallel runs and optimization
16. 35:54Monolith testing and feature branches
17. 39:46Summary and recommendations
18. 41:13Q&A

" related talks

• 47mTesting: How We Developers Do It on the BackendRobert Podsiadły · 4Developers 2020
• 43m"Monoliths are Simpler" and other lies we tell ourselvesPhil Calçado · Craft Conference 2021
• 48mMake your tests tell the story of your domainMads Opheim, Anne Landro · NDC TechTown 2019
• 57mEnd-to-End Automated Testing in a Microservices ArchitectureEmily Bache · NDC Oslo 2017
• 38mScaling Automated Testing & Architecture from Startup to EnterpriseApostolos Giokas · Voxxed Days Thessaloniki 2023
• 43mBreak Up the Monolith: Testing MicroservicesMarcus R Merrell · Selenium Conference India 2018
• 35mTesting Strategies for Giant ApplicationsAndrea Natalia Naranjo Chavez, Amanda Ramirez · DrupalCamp Spain 2023
• 47mBreak Up the Monolith: Testing MicroservicesMarcus R Merrell · Selenium Camp 2019