2024-Emerging-Wolf-Macielinski
summary
QA automation Engineers own end-to-end automation and push testing down the pyramid, using Cucumber BDD for component tests and JUnit for integration while running hundreds of test cases in seconds or minutes in CI. Hardware-dependent systems use a simulator code module instead of mocks; UI checks use Selenium/Cypress and analytics verification (PDFs) remains hard. CI failures force triage—about 12 flaky failures can block a release—and allure reporting helps prioritize fixes.
AI-written summary · about
chapters (12)
- 0:00Component testing
- 0:23QA automation role
- 1:31Behavior-driven testing
- 2:37Integration with simulators
- 4:23Component vs integration tests
- 5:04Pairing QA and automation
- 6:30Triaging brittle tests
- 7:33Slow test fixes
- 8:15E2E testing real world
- 9:18Analytics validation automation
- 10:00UI testing challenges
- 16:53Testing pyramid
related talks
48mBeyond Bugs: How AI Turns QA into Full-Cycle Engineers
53mTransforming testing methodologies: From manual to robust strategies
38mScaling Automated Testing & Architecture from Startup to Enterprise
45mSpyros Katopodis: How You Should Be Using Agile and AI For Testing And Quality Assurance
46mSoftware Devs in Test Automation - Dream or Reality in Agile Software Dev?
55mQuality Engineering Evolution: What Lies Ahead in
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
24mWHY ARE WE FAILING WITH TEST AUTOMATION?