4 ms·
'Test Pyramid' considered harmful IMO. It discourages people from writing tests against the public interface of their system , and instead encourages testing ag
by macca321 8y ago
'Test Pyramid' considered harmful IMO. It discourages people from writing tests against the public interface of their system , and instead encourages testing against internals.
This leads to a test pack that prevents refactoring, and can't be trusted to catch regression errors.
This is partly down to the widely confused definition of a 'unit test' (which a lot of people interpret as 'one test per class').
If you haven't seen it, please watch Ian Cooper's "TDD, Where Did It All Go Wrong" https://www.youtube.com/watch?v=EZ05e7EMOLM https://www.youtube.com/watch?v=EZ05e7EMOLM
Also, I thought continuous testing was having your test pack run all the time while coding, but hey ho.
- TarpitCarnivore 8y agoTBH I feel like integration and UI tests can be combined at this point. Writing a bunch of tests to only check UI elements feels like a waste to me. I don't mean to go full on BDD where every step is spec'd out, but I've done it by interacting with elements and validating data with the API.