Testing for products with a microservice architecture
summary
Twitter builds a decentralized web test framework called webtf on TestCafe, publishes versioned component libraries via npm, and wires in BrowserStack and visual reporting so teams skip infra work and share page objects and utils. Versioning prevents one change from breaking everyone; component libraries let teams pick the feature version they need. The goal is to approach ~99.9% reliability by shifting teams to write focused tests; early feedback says adoption is faster and tests are easier to maintain.
AI-written summary · about
chapters (15)
- 0:00Introduction and speakers
- 1:04The decentralized testing monster
- 3:51Twitter’s startup origins
- 5:54Challenges of decentralized teams
- 10:11Cascading failures in testing
- 13:41Limitations of single-team frameworks
- 17:33Building a decentralized framework
- 19:17Framework infrastructure design
- 23:28Team interface with the framework
- 24:30Teams focus on business logic
- 27:21Reusable components and libraries
- 28:45Health of automated tests
- 32:16Impact on teams and adoption
- 35:05Feedback from teams
- 37:36Closing and Q&A intro
related talks
45mTesting the web without testers — success or failure
38mModern Web Testing: Going Beyond Selenium
45mTesting Big in JavaScript
53mModern Web Testing: Going Beyond Selenium
34mEnd to end testing a world of web, mobile & desktop apps
55mModern Web Testing: Going Beyond Selenium
49mTestCafé: Web Testing Made Easy!
29mState of Web Integration Testing