State of Web Integration Testing

on YouTube ↗29m

" summary

Five months of research (two months research, three months building) produce a working integration test framework that runs 11 months in production for a surgery‑services web app and exposes concrete tradeoffs: use the Selenium/WebDriver stack for real cross‑browser coverage, use PhantomJS/CasperJS for fast smoke checks but accept PhantomJS is not full integration testing, prefer hosted CI or VM providers for scale, and move toward component‑level automation where each UI component ships its automation description.

AI-written summary · about

" chapters (7)

1. 0:00Start
2. 0:20State of web integration testing
3. 1:39Vocabulary
4. 15:13Complexity
5. 15:38Cucumber
6. 20:34Reliability
7. 26:27Recap

" related talks

• 04mWe're bad at web integration testingMatti Schneider · dotJS 2013
• 53mModern Web Testing: Going Beyond SeleniumDmitry Vinnik · GeeCON 2019
• 55mModern Web Testing: Going Beyond SeleniumDmitry Vinnik · NDC Minnesota 2019
• 38mModern Web Testing: Going Beyond SeleniumDmitry Vinnik · Voxxed Days Frontend Bucharest 2019
• 30mModern Web Testing: Going Beyond SeleniumDmitry Vinnik · DjangoCon US 2021
• 36mModern Web Testing: Going Beyond SeleniumDmitry Vinnik · TestCon Vilnius 2018
• 32mAll about web application testingAnisha Narang · FOSSASIA 2015 DevOps Track
• 45mTesting the web without testers — success or failureTatyana Ryzhenkova, Sergey Zvyagin · FrontTalks 2016