Risks with Ticket Driven Software Testing
summary
Over 100 task analysis interviews find that ticket-driven testing with tools like Jira Microsoft DevOps and Git workflow systems narrows scope so testers see one ticket not the architecture or integration risks. The study lists 12 risks identified including missed cross feature interference and resource sharing, tickets prompting focus on closing rather than quality, and long clarification chains of 30–100 question threads. “Ready for testing” often means the latest possible start and the model fragments knowledge and collaboration.
AI-written summary · about
chapters (5)
related talks
28mRisk Based Testing in Agile Teams
40mRisk Based Testing in Agile Teams
01h 34mShift left in testing: Find bugs before they’re implemented
49mThe Secret to Successful Testing
44mFive Key Challenges for Agile Testers tomorrow
50mThe End of Testing as We Know It
22mOvercoming the obstacles of Exploratory Testing at scale
32mTDD – Trust Driven Development