There's plenty of training available because there are plenty of people trying to make money selling it, but I can't think of a single one I'd recommend. If the

There's plenty of training available because there are plenty of people trying to make money selling it, but I can't think of a single one I'd recommend. If the "good" training is out there I certainly haven't seen it. Part of the problem is the inconsistent role of the tester. In some organizations testers are there to ensure the requirements are fulfilled. In others they are truffle pigs for bugs. Some testers are expected to keep their testing black-boxed and high-level, while other testers are expected to help troubleshoot the bugs, the environments, and the CI pipelines. My advice to you (as a developer, I presume) is to stop relying on others for testing. Pretend they don't exist. With every commit you make you should assume it's heading straight to the production environment. So you need to have confidence not only in your unit of code, but also in the behavior of the system as a whole before you submit your pull request. I am a tester, not a developer, but from my perspective TDD is the way a developer should go. The highest-quality products I work on are the ones where my testing is the least needed. If I'm bored that's usually a good thing.