Strategic Business Functionality Testing: Accelerating Development Through Mocking
summary
Claims a homegrown proxy called Mox replaces fragile end‑to‑end dependencies with mocked REST/SOAP stubs, parses XML to JSON, and auto‑collects real responses so developers stop hand‑crafting fixtures. It ships in three weeks, runs as NodeJS + Docker + pm2, supports COT SAP Salesforce integrations across 56 resorts, yields 24% runtime reduction, produces 10 stable E2 tests and uses K6 and Playwright for load and UI runs, and it noticeably survives core system outages.
AI-written summary · about
chapters (24)
- 0:00Business testing with Mox
- 1:49HappyMac testing problems
- 3:15HappyMac core systems
- 8:53Legacy testing challenges
- 10:21Imposeter limitations
- 14:28Custom mocking microservice
- 15:34Mox technical overview
- 18:47Custom mocking advantages
- 21:24Mocking libraries management
- 22:31Mocking staging environments
- 23:34Results and benefits
- 25:02Mocking performance testing
- 27:56Key takeaways and future
- 28:40Q&A
- 29:02Performance testing start
- 30:07Monolith testing groups
- 31:13Why K6 chosen
- 31:34Mocked vs end-to-end tests
- 33:20Mocking microservices
- 34:03Mox performance bottleneck
- 35:31AI in mocking approach
- 36:14Performance data generation
- 38:07Production performance mocking
- 39:09Q&A and closing
related talks
25mFakes over Mocks: Shift your paradigm and identify monolithic code
28mGenerating Test-Cases and Mocks from Production
37mStop Doing E2E Tests! Write Better Tests with Contract
27mNo More Mocking! Write Better Tests For Your Nuxt Application With Contract Tests
51mAutomatic testing of a heavily integrated system - a case-study
36mAPI Testing Without Writing Test Cases and Mocks
11mHow to make cheap e2e tests
01h 05mMicrotesting