End to End Automation from a Developer Standpoint
summary
Team builds end-to-end browser tests using Playwright with Python, runs them against staging and protects isolation with a drop-and-reset staging API that wipes and presets the database before each test. Tests use data-test-id selectors and page objects, live in a separate repo, and number about 100. CI runs as a nightly GitHub Actions job producing screenshots for visual regression; heavy setup is moved into an SDK and API-only stress tests measure backend limits.
AI-written summary · about
chapters (33)
- 0:00Introduction
- 0:27About the speaker
- 1:09Mission critical systems
- 3:38Manual testing approach
- 5:22Need for automation
- 6:05Automation goals
- 7:07Weakest integration points
- 8:10Choosing Playwright
- 10:16First automated test
- 11:37Shared state problem
- 12:41Database reset solution
- 13:03Complex signup flow
- 14:28Third-party integration challenges
- 15:10Testing on staging
- 15:51Concurrency limitations
- 17:14Maintainable test structure
- 18:41Environment configuration
- 19:22Page objects abstraction
- 20:04Selector strategies
- 21:07Data-test-id benefits
- 22:30Frontend and test sync
- 23:32Test setup complexity
- 24:57SDK for test setup
- 26:01UI vs API for setup
- 27:04Test repository location
- 27:46Running tests on CI
- 28:49CI scheduling strategy
- 30:31Visual regression testing
- 31:56Screenshot review process
- 32:59AI for UI regression
- 33:41Stress testing importance
- 34:45API tests for stress
- 35:27Conclusion and investment
related talks
35mState of end-to-end testing for modern web applications
41mTesting Web Applications with Playwright
30mTesting Web Applications with Playwright
30mPlaywright: The Tool That Will Revolutionize End-to-End Testing
10mCreate, Run and Deploy end-to-end tests with Playwright and GitHub Actions
34mEnd to end testing a world of web, mobile & desktop apps
16mEnd to End testing with Playwright
26mAutomated E2E Testing with Playwright and Python