Automation backlog HandlingHome › Forums › Software Testing Discussions › Automation backlog HandlingThis topic contains 3 replies, has 3 voices, and was last updated by Tassawer 2 years, 2 months ago. Viewing 4 posts - 1 through 4 (of 4 total)Author Posts June 8, 2017 at 1:52 pm #16447 TassawerParticipant@tassaweraminHi,What are the best practices to handle automation backlog and separate them from product backlog.One of the approaches is to create automation sub-task in every User story.Whats your approach? What are pros and cons of them ? June 22, 2017 at 4:29 am #16516 ArchanaParticipant@archanaFound an article that may helpful. You can read it here. June 23, 2017 at 10:34 am #16539 PalaniParticipant@tmpalaniselvamif you create automation as sub task for each user story, then you should do in-Sprint automation.Otherwise create separate backlog for automation and track the status. June 26, 2017 at 10:43 am #16555 TassawerParticipant@tassaweramin@archana Thanks 🙂Author Posts Viewing 4 posts - 1 through 4 (of 4 total)You must be logged in to reply to this topic.