BACKGROUND
In the [RFC-232] , [RFC-268] style tests we wanted to simplify some of the abstractions around testing, so it is simpler to implement, and the ecosystem gets out of the way more. This led to a paradigm shift from "I'm doing an x-style test", to "I'm testing X and need Y and Z configured in order to do it". E.g moduleForComponent
-> setupRenderingTest
, moduleForAcceptance
-> setupApplicationTest
.
In implementing the new style blueprints for ember-data, I'd like to understand where we'd like the ember-data testing story to go, and if this is the right point to do so, since we will be modifying those files.
As such, what are analagous concepts we could introduce for ember-data? Does it make sense to introduce these analagous concepts?
Ember Data Classes Who's Testing Use Cases We Need To Ensure We Address
- Adapters, Models, Serializers, Transforms