Developing an Ember Test Strategy
summary
Argues for tight feedback loops and a test distribution that keeps runs short: Ember provides unit, rendering, application tests and a 1,000-test run shows application tests ≈33 minutes while units are near-instant. Recommends pushing logic down the pyramid (examples: profile-page component split into upload-picture component; chat service mocked into realtime, profile, history collaborators), using Testem, segmentation and multithreading, favoring TDD or mock-driven tests as needed and deleting slow, low-value tests.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:11Ember Loves Tests
- 3:51Speed and Feedback Loops
- 4:14The Deming Circle
- 4:58Continuous Improvement
- 6:40Feedback Loops
- 8:18The Agile Manifesto
- 9:09Agile Testing
- 14:06Test Workflow
- 16:10Lump of Code Fallacy
- 19:24Inside-Out Programming Model
- 25:24Working with Legacy Code
- 26:41Summary
related talks
36mUsing Tests as a Tool to Wrangle Legacy Projects
31mThe Unofficial, Official Ember Testing Guide
16mTest as if you're in someone else's shoes
25mTest-Driven Development of Ember.js Applications
21mTesting against time in JavaScript applications
28mThe Next Generation of Testing
22mTest Effective Development
30mTesting Front-End Applications