How to Make Developers LOVE Writing e2e Tests
summary
A team at wix.com moves end-to-end ownership from QA (Java + Selenium) to developers, switches test tooling and some QA to JavaScript, and reports concrete wins and risks: faster delivery if developers write reliable tests, or disaster from flaky suites. Key practices are design coverage centrally by QA, build short and focused end-to-end tests, keep environments isolated and review flakiness constantly, teach developers test-writing patterns and code conventions, and start reputation-building with one good test.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:03What is Velocity
- 9:07Benefits
- 11:00Reactions
- 18:31How to make it work
- 26:30Scalability
- 29:04Best practices
- 31:08Review
- 32:54Developer Mindset
- 36:03Make it a habit
- 37:36QA Engineer in this process
- 39:33Key takeaways
related talks
41mEnd-2-end testing without the pain
34mWriting end to end tests with a smile
45mMake Your Interfaces Reliable by Getting Your Team to Love Tests!
36mWhole team quality: In the same boat or up the creek?
25mWriting end to end tests with a smile
01h 01mHow to (Not) Use Testers Properly
16mEnd the Test Engineer role: how cross functionality leads to a better engineering
53mModern Web Testing: Going Beyond Selenium