Some good points in this list although I'm not in full agreement with everything (especially the one about the lack of usefulness for TDD). The importance and the impacts of the tooling is often underestimated indeed. The last two random opinions about mocking and overtesting are very much true as well.

Very interesting musing about the technical terms we often use wrongly and how it difficult it is to be understood.

I don't quite subscribe to some of the terms used (even though I see the point of not calling this API). Still I think this is a very good way to approach design, it's also why I like TDD, the tests force you to see how the code is used. If it ain't pretty there's a problem.

Likewise I'm more and more unconvinced about the unit vs integration tests distinction. It's likely a continuum between them. I like the proposed axes for classification here. I wish they'd be a bit more orthogonal though.

Very good reminder that as an industry we're quick to blame external factors for our own failures. Of course we can be given a bad hand, but sometimes we'd have failed with a good hand as well.

Nice application for testing APIs.

Interesting musing on the skills required, why it's actually hard to apply them... clearly it's because you never find a real place to learn them so that ends up being on the job.

Good guidelines to improve end to end tests. I especially relate to the first one, the test API is very important for those, otherwise they become a chore to maintain and understand.

Mostly about the general approach on how to profile this kind of things. Still a couple of interesting pytest specific tips in here.

Looks like an interesting tool, it's always a bit of a problem to simulate various network conditions, especially slow links randomly dropping packets. Adding more tooling to tackle this is always welcome.

Looks like an interesting tool for testing when a HTTP server is involved.

Interesting coaching approach for teams. It's indeed hard to get teams to stick to some of the difficult development practices... By mixing several approaches, this looks like she's onto something here.

More on the test pyramid debate... As usual looking at the history of a concept and carefully evaluating how things are named is very enlightening. This is a must read.

I've been banging the testing drum for so long I'd have a hard time to not violently agree with that article. I have a couple of beefs with it though, like the sacrificing encapsulation point but other than that...