Discussion about this post

User's avatar
Anupam Krishnamurthy's avatar

Fantastic read! At my ex-employer, we did switch from a siloed role to being a quality team that leads testing initiatives. There is, perhaps, scope to go even further. When product teams are mature enough, they can handle, and sustain test coverage / test suites even without an embedded quality specialist on the team. The quality engineers can instead steward the processes and build the test infrastructure necessary for product teams to serve themselves. Is that a fair perspective?

Expand full comment
Jit Gosai's avatar

Thanks for sharing, Alessandra. I completely agree with having an automation goal before starting - so many teams miss this and assume everyone is expecting the same outcomes with automation.

I particularly liked what you should cover during whole team discussions: Layers of testing, critical paths, and priorities all help build that joint understanding of what will and will not be covered and how it helps the team achieve their goal, too.

Looking forward to hearing more from you

Expand full comment
3 more comments...

No posts