Our testing philosopy and policy is explained in the following documents:
https://github.com/cfpb/cfgov-refresh/blob/master/TEST.md
https://github.com/cfpb/front-end/blob/master/testing.md
I would only add that our Acceptance tests should focus on testing functionality and dom structure. Testing content becomes tricky because it's constantly changing via the CMS or some other channel. This is demonstrated in the following example:
Bad
it( 'should properly load in a browser', function() {
expect( page.pageTitle() ).toBe( 'The Bureau' );
} );
Good
it( 'should properly load in a browser', function() {
expect( page.pageTitle().isPresent() ).toBe( true );
} );