- This topic has 3 replies, 3 voices, and was last updated 7 years, 2 months ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
Home › Forums › Software Testing Discussions › Automation backlog Handling
Hi,
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 ?
if 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.