Measuring Performance, JavaScript Games, and Distributed Testing
summary
Shows concrete problems and fixes: built a jQuery stack‑profiler plugin and a Firebug extension that exports profile data as JSON, finds algorithmic hotspots (for example remove optimized n^2 → 3n), and avoids misleading millisecond timing on Windows where timers update only every 15 millisecond timer granularity. Demonstrates a Guitar‑Hero canvas demo that fails with GC pauses, hides a Konami‑code game on the jQuery homepage, and ships Test Swarm, a working distributed continuous test platform that runs real browsers and mobile devices though it faces scaling and fault‑tolerance work.
AI-written summary · about
chapters (19)
- 0:00Start
- 0:26Measuring Performance
- 1:39Stack Profiling
- 5:50Performance Tools + How can we get good numbers + We have to go straight to the source: Use the tools the browsers provide.
- 6:15Firebug Profiler
- 6:35IE 8 Profiler
- 7:24FireUnit Profile Data
- 8:12Complexity Analysis
- 12:44Goals of a game
- 14:24Nile Online
- 14:39Strategy Games
- 15:05Intelligence Games
- 16:22Iron Sudoku
- 22:30Wordsplay
- 32:43Cost / Benefit
- 33:39Graded Support
- 33:57Browser Support Grid
- 36:47The Scaling Problem
- 37:08Distributed Testing
related talks
21mBenchmarking Like a Boss
21mWorking Well, The Future of JavaScript Testing
43mAutomated Performance Testing With WebDriver
57mPanel 7: Testing and tooling
30mJSConf 2015 Dave Cadwallader
32mDevelop Your Own Performance Tool Integrated with Selenium
37mFront-end Testing for Skeptics
37mAutomated Performance Testing With WebDriver