Intro to Client-Side Testing
summary
A minimal single‑page app with drag‑and‑drop file uploads backed by a REST API using JSON web tokens is built and mostly works; end‑to‑end Selenium integration tests run in PhantomJS to log in, fill forms, wait for DOM changes and assert visibility. Isolated client logic gets QUnit unit tests for Backbone models and views with patched collection calls to fake API behavior. Tests run slowly (setup once per class) and leave a few 404 paths uncovered.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:43Goal
- 1:25Project Overview
- 2:11Guest Login
- 3:47Selenium Setup
- 4:40Selenium Test
- 5:11Forms
- 8:24Selenium assertions
- 9:30JavaScript testing
- 10:46Why Qunit
- 12:03Setting up Qunit
- 13:06Qunit Test
- 14:17Setup and Teardown
- 16:49Bonus
- 17:51Drag and Drop
- 18:58Queue Unit Tests
- 19:31selenium
- 20:14unit tests
- 21:15Resources
related talks
36mModern Web Testing: Going Beyond Selenium
37mFront-end Testing for Skeptics
45mTesting Big in JavaScript
14mDebugging Secrets of a Lazy Developer
45mEnd to End testing React applications
27mAutomated Testing for the Modern Web
46mBuilding Tests to Build Websites
34mEnd to end testing a world of web, mobile & desktop apps