@samselikoff I posted some thoughts on testing Ember apps here: http://pixelhandler.com/posts/testing-an-ember-application-integration-and-unit-tests
The article needs updating or perhaps a follow up article with current helpers, ember-testing setup etc.; But I did include a section Testing Strategy which lists my opinions about testing an ember app.
I recently recorded a quick screencast on integration testing with Ember here: http://vimeo.com/86432032 The client-side testing starts about 3 mins into the 6 min video (first half is server tests)
As for testing HTML… When writing integration tests, I like to test the result of my rendered templates. So I may assert / expect some text or css classes are present. However I do not test CSS, except for things like hide/show etc.
If you are interested in reviewing test code for an ember app, my blog is written with Ember and I have an integration test suite written for the app shared at: https://github.com/pixelhandler/blog/tree/master/client/tests/integration
My approach to integration testing with Ember is to test for each feature, starting with the simplest thing like a list of links in a menu, then move on to a button that loads more, then perhaps a login form, next the create, edit, delete actions for a web form… and so on. The integration test suite should grow with the set of features. I also like to write the test (failing) then write the feature to pass the test (TDD). However when trying to figure out how Ember works I may just build a part of a feature then once I figure out how the feature is supposed to work in Ember I write a test and continue, etc.
Hope this helps you with your testing strategy.