'Test Pyramid' considered harmful IMO. It discourages people from writing tests against the public interface of their system , and instead encourages testing against internals.<p>This leads to a test pack that prevents refactoring, and can't be trusted to catch regression errors.<p>This is partly down to the widely confused definition of a 'unit test' (which a lot of people interpret as 'one test per class').<p>If you haven't seen it, please watch Ian Cooper's "TDD, Where Did It All Go Wrong" <a href="https://www.youtube.com/watch?v=EZ05e7EMOLM" rel="nofollow">https://www.youtube.com/watch?v=EZ05e7EMOLM</a><p>Also, I thought continuous testing was having your test pack run all the time while coding, but hey ho.
I like test recorders (Selenium IDE). They aren't brittle if you manually enter your selectors. Plus you can hook a test recorder up to your own code to fill in any gaps. I do wish they showed mouse movement, though.<p>One I'd like to add is to keep it simple. When I hear the word pipeline I immediately think "oh no". I'm telling you man, some shops add a mind blowing amount of unneeded complexity with their pipelines.