Yeah, that’s been my experience too. Once tests, results, and acceptance criteria are tied directly to the repo and PR flow, there’s a lot less manual updating and chasing status. The tricky part is finding the balance enough structure to give visibility, but not so much process that it turns into busywork. Curious how others here decide when that extra tooling actually starts adding value instead of friction. I’m familiar with TestRail since it’s been around for a while, but I haven’t come across QualityFolio before. Would be interested to hear how it fits into this kind of code centric workflow and what problems it’s aiming to solve!