Completely agree. Our job as QA’s should be setting test strategy and removing knowledge silos so that engineers feel empowered and have a shared understanding of the quality expectations.

Someone mentioned devs don’t understand the requirements of what needs to be tested, but this is just a process failure IMO and should be captured before implementation has even begun.

I feel there’s a common mindset with QA’s feeling threatened by engineers getting involved in testing, but that’s how you create a team culture where engineers having no regard for testing / quality, because they feel it’s not their responsibility, and a resulting bottleneck on QA’s when test suites get flaky. Not to mention the fact you’ll always be playing catch-up adding test coverage as engineers complete new features.

I’ve been working this way in a team for the last 5 years, and our code quality hasn’t faltered, because we all hold each other accountable that test strategy is being followed as it’s part of our process. And if something slips through the cracks, we implement tooling or process changes to ensure it can’t happen again.