Very interesting research. Property-Based Testing made quite some progress the past few years but indeed it still needs to improve in term of usability. Looking forward to some of that research to get available in existing testing tools.

Another rebuttal of Clean Code. Most of it makes sense if not overdone. There's the usual confusion around the "unit tests" term though, so take that section with a pinch of salt.

A nice list of the techniques used to render shadows in games.

Indeed a good way to reason about tests and the value they bring.

Another example of why pytest is really a nice test runner. I really miss it on projects which don't have it.

This is an important trait to have for a developer. If you're content of things working without knowing why and how they work, you're looking for a world of pain later.

This could be a game changer to collaborative editing. Clearly a good competitor to CRDTs, should make it easier to build such features without a central server.

That sounds like a very interesting tool to simulate and test potential data loss scenarios. This is generally a bit difficult to do, should make it easier.

Interesting reason which would explain the Selenium flakiness. It's just harder to write tests with race conditions using Playwright.

This can definitely come in handy. I can see myself using it for testing behaviors in the past or the future on a real application. This should also help writing automated tests in some cases.

Three good advices on writing automated tests. This is necessary but not sufficient though.

Starting from a wrong analogy to raise real thinking and questions about TDD.

Interesting tool for diffing database tables. Should come in handy for tests.

Ever wondered where fuzz testing is coming from? This is an important bit of history.

This is a technique which is definitely underestimated. There are plenty of libraries out there allowing to use them.

Good advice indeed. Having asserts using appropriate matchers can go a long way understanding what went wrong.

Maybe a bit dry, but gives a good idea of how a fuzz testing harness works. And also how it can be tweaked.

Interesting use of database templates and memory disks to greatly speed up test executions.

This is indeed too often overlooked. Producing a test list and picking the tests in the right order is definitely a crucial skill to practice TDD. It goes hand in hand with software design skills.

Indeed, don't mindlessly add tests. I find interesting that the doubts raised in this piece are once again concluded using an old quote of Kent Beck. What he was proposing was fine and then over time people became clearly unreasonable.