http://www.confreaks.com/videos/299-lsrc2010-grease-your-suite-tips-and-tricks-for-faster-testing
seems to not like mocking much
talk-grease-your-suite#before-all-and-fast-contexts1 talked about the same before :all trick that we use to good effect in a lot of places and gave it the name "fast contexts". talk-grease-your-suite#before-all-and-fast-contexts1
talk-grease-your-suite#ci-lag1 "Continuous integration is great. Working, testing, And then committing tests and code. Always works real nice. The problem is when you're working for 30 minutes and then our test take 30 minutes it's just not really a very efficient process. So at that point a lot of people say hey let's build the CI server to run a test for us. The CI servers are helpful for running code in production environments but this usually ends up getting you out of sync with your usual testing process so your feedback loop is still 30 to 40 minutes behind." talk-grease-your-suite#ci-lag1
The other thing that I don't like about relying on CI is that you're pushing untested code out into the world (if you're committing on master and relying on CI to catch the issues). Other developers could pull that bad master commit before the build breaks.
Probably this talk, but maybe another one, at 16 minutes he talks about not testing the public API.
He also talks about "empty database" tests (where you factory everything in)