From 0 to 100: How We Jump-Started Our Frontend Testing

on YouTube ↗41m

" summary

Doist built an automated frontend testing pipeline that runs unit, component, and integration checks in CI. The pipeline uses Chrome and Firefox locally, WebDriver plus cloud VMs to test Safari and Internet Explorer, and a Jenkins pipeline to run snapshot tests and assertions against snapshot files, producing faster refactors, fewer user bug reports, and coverage metrics for shipped components.

AI-written summary · about

" chapters (11)

1. 0:00Frontend testing journey
2. 4:44Code quality boost
3. 9:21Cross-browser challenges
4. 13:18Baseline safety tests
5. 16:24Unit vs integration
6. 20:23Testing pipeline setup
7. 25:54Future testing plans
8. 28:52Button interaction tests
9. 31:41Debugging disabled features
10. 35:20Q&A
11. 40:54Summary

" related talks

• 35mTesting in Frontend WorldNykyta Halkyn · Frontend fwdays'17
• 50mFrontend-as-a-Service Automated Testing: Layers and CI PipelinesDzmitry Prakapuk · DelEx Conference 2020: DevOps & Test Automation
• 49mFail Fast Approach in Frontend DevelopmentVitali Lashchanka · RS Conf 2019
• 28mUsing CI to Test the Frontend: the TeamCity ExampleDenis Lesnik · JetBrains Open Day 2019
• 45mTesting the web without testers — success or failureTatyana Ryzhenkova, Sergey Zvyagin · FrontTalks 2016
• 19mWorking Well: The Future of Web TestingTrent Willis · dotJS 2017
• 53mModern Web Testing: Going Beyond SeleniumDmitry Vinnik · GeeCON 2019
• 38mModern Web Testing: Going Beyond SeleniumDmitry Vinnik · Voxxed Days Frontend Bucharest 2019