Saying goodbye to full stack tests with task analysis
summary
Full-stack Selenium login test splits into four targeted checks: a visual screenshot check with Applitools against the Restful Booker Platform, an API check using REST Assured validating 200 + token, a unit controller test with JUnit that runs in ~10 ms to assert token generation, and a React component snapshot via Enzyme. The method uses task analysis to map seams, applies TRIMS (targeted, reliable, informative, maintainable, speedy), and composes a chain-of-trust so one small smoke check suffices.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:48How do we know if a check is valuable
- 2:19Demo
- 4:53Characteristics
- 8:32Speedy
- 9:35Trims
- 10:51Implementing valuable checks
- 11:05Task analysis
- 13:20Task analysis model
- 21:38Visual check
- 24:10Applitools
- 26:22HTTP layer
- 27:30Rest assured
- 30:28Unit checks
- 33:31Final check
- 34:41Final test
- 36:10Chain of trust
- 37:55Wrap up
related talks
47mFull-Stack Test Automation
37mAdvanced Test Automation Techniques for Responsive Apps and Sites
41mWriting Well-Abstracted Self-Testing Automation On Top Of Jello-O
41mAdvanced test automation techniques for responsive apps and sites
50mAsaf Shochet Avida, Eitan Noy: Why My Amazing Test Automation Project Crumbled
27mTest Effective Development - End 2 (What) End?
41mFunctional Tests (Selenium) in Practice
37mSelenium In the Enterprise: What went right, what went wrong (so far)