Automated Tests Across the Galaxy
summary
Talk explains building a systematic automated testing system around end-to-end (E2E) tests for JavaScript projects, addressing flaky or failing E2E suites and maintenance overhead. It focuses on practical practices and responsibilities for JS developers to diagnose failures, understand root causes, and keep the E2E test system reliable.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 3:12Automated tests matter
- 6:21Untested code fixes
- 9:36Smoke tests
- 12:01Page Object Model
- 14:06Mocks in frontend
- 15:10Setup test specifics
- 16:37Diagnostics after tests
- 17:40Chaos in tests
- 20:34Test pyramid
- 21:59Behavior Driven Development
- 24:29Engaging analysts
- 27:01Business vs dev testing
- 28:47Automated tests ROI
- 31:04Q&A
- 33:09Testing pyramid ratio
- 34:33Convincing business
- 36:22Page Object Model
- 38:57Avoiding meta-tests
- 40:00QA-automator role
- 41:22Time for automation
- 42:25Process changes load
- 43:27Mocks for backend
- 44:30JSON server alternatives
related talks
37mThe Journey of End-to-End Automated Testing
47mFull-Stack Test Automation
48mit('should be easier') Automated testing in the real world
42mSurviving the JS Testing Tools Jungle
20mPanel Discussion on Testing
54mSurviving the Underworld of End-to-End Tests
45mWriting Tests That Don't Suck: TDD in JavaScript
27mTest Effective Development - End 2 (What) End?
