How Not to Fear Breaking Production? QA Automation Lessons with Testplane
summary
Describes how Yandex teams automated QA to avoid breaking production using Testplane. Covers using Storybook to create no-code smoke-test coverage, why running component tests in real browsers is more reliable than jsdom, strategies to reduce pain with flaky e2e tests, issues with screenshot tests, reproducibility across test environments, and reasons for building the in-house e2e framework Testplane.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:10Frontend testing speed
- 5:44Testplane features
- 8:12No visual test solutions
- 13:37Visual tests in minutes
- 14:19Speed visual checks
- 17:52Screenshot comparison
- 23:54Visual test results
- 24:15Component tests vs JSDOM
- 27:51Hot Module Replacement
- 29:13E2E tests with Yandex.Search
- 31:01Speed up CI tests
- 32:47Fix test instability
- 35:42Mock external requests
- 37:30Cross-browser and mobile
- 39:18Debugging tools
- 41:46Summary
- 42:28Q&A
related talks
53m20 QA Best Practices to take back to your workplace
33mTESTING IN PRODUCTION
56mNo QA resources? You can still deliver a quality website
36mTesting In Production
50mAsaf Shochet Avida, Eitan Noy: Why My Amazing Test Automation Project Crumbled
39mBuilding The Blocks of Trust In Automation
25mTesting in Production
54mTest Automation Transformation Avoiding the 7 Common Pitfalls
