Stop Asking QA to Find Your Bugs. Learn to Write Tests Yourself.
If you looked at our Jira board from eighteen months ago, it told a very sad, very common story.
The "In Progress" column was humming with activity. Developers were churning out features, closing tickets, and proudly moving cards to the right. Velocity looked great on paper.
But the column immediately next to it, ominously titled "Ready for QA," was a black hole where momentum went to die. At one point in Q3, we had 42 tickets sitting in that column. We had an organizational ratio of roughly six backend and frontend developers to every one QA engineer. The math simply didn't work. It was never going to work.
A feature would take a developer three days to build, and then it would sit completely idle in the QA queue for two weeks. When a QA engineer finally had bandwidth to pick it up, they would inevitably find a bug—often a...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
