> First: it's not the best use of our time. I believe dev and QA are separate skillset. Of course there is overlap. I've heard this comment before,and it fails

> First: it's not the best use of our time. I believe dev and QA are separate skillset. Of course there is overlap. I've heard this comment before,and it fails to hold in practice. You are not making the best use of your time if your ticket is blocked because you were paired with a QA who is sitting on a ticket, or is oblivious to the problem domain to the point he struggles to put together a single test that is relevant. You are also not making the best use of your time if a test suite is not maintained by said QAs and fails in pipelines without anyone acting on it. For verification and validation tasks, and if QAs treat pipeline maintenance as an OnCall rotation, that would hold true. Anything beyond this, a QA can waste far more time than the one they could hypothetically save you.