The Unofficial, Official Ember Testing Guide
summary
Claim: Ember testing becomes practical now with concrete tools and patterns the guide actually ships — QUnit assertions plus Ember's helpers visit fillIn click andThen drive integration flows while ember-qunit (moduleFor) creates an isolated container so unit tests run without loading the whole app. New helpers include triggerEvent currentRouteName currentURL. Examples live as runnable jsbins, ember-qunit is in Ember App Kit/CLI, and the approach consistently creates subjects and tears down the sandbox so tests work deterministically.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:25Ember developers need testing
- 3:50Assertions and helpers in Ember
- 8:13Custom helpers and types
- 11:42Ember 1.5 testing helpers
- 13:59Integration vs unit tests
- 16:34Unit testing challenges
- 18:24Introducing ember-qunit
- 21:38How module-for works
- 23:03Unit testing routes/controllers
- 24:26Testing components
- 25:50Unit testing Ember Data
- 26:37Future of testing guide
- 27:43Q&A
related talks
20mEasy-Bake Testing
28mDeveloping an Ember Test Strategy
28mThe Next Generation of Testing
21mTesting against time in JavaScript applications
25mTest-Driven Development of Ember.js Applications
16mTest as if you're in someone else's shoes
24mNew to Ember: What ARE All These Things?
36mUsing Tests as a Tool to Wrangle Legacy Projects