Testing the Waterhouse

I'm sure you've all heard of the automated testing pyramid, I'll describe it briefly here, but you can read all about it here . It's essentially a strategy that shows good practice ratio of Acceptance Tests (generally UI) to Integration Tests to Unit Tests, and here it is here in a simple form. It states that it is a good ratio to have your testing covered with 10% of acceptance tests, 20 % integration tests and 70% unit tests. Why is that you may ask? The primary focus of this is on Return on Investment, by finding bugs/breakages at Unit test level you are finding cheap bugs, as Unit Tests are quick and easy to maintain, whereas acceptance tests, whilst having value, are harder to maintain and take longer to run. Obviously, it's not a strict ratio, but I think it's a good practice to try and live by. However, I digress, the main point of this post is to put another spin on the automation triangle, and is possibly more QA centric than the automation ...