Yeah for sure, I agree, very helpful info.  And to @coderstash and @JulianLeviston's point we could create a `Testing Ember.Object` page and drag half of these tests into them, then in the `Testing Controller` and `Testing Route` we could just give some sort of reference such the statement we've been modifying above "Unit testing methods & computed properties follows previous patterns because Ember.Controller extends Ember.Object. See `Testing Ember.Object`"  The rest of the info in the document could be testing nuances that don't exist in normal Ember.Object such as needs, model hooks etc.