Ember has an amazing testing story built upon the fundamentals of encapsulation and OO programming central to the framework. Despite this, every web application will be dependent upon and need to interact with native and network APIs that are hostile: Unreliable, slow, under-documented, and not to be trusted. The challenge in testing Ember applications lies with how to handle these external entities.
In this talk, we distinguish the domain of an application from its implementation dependencies. The dependency is contained such that it avoids leaking into application code, unit tests, and acceptance tests.
Your new post is loading...