Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We are adopting BDD using specflow. The issue we have is that product owners and managers can not be expected to go into Visual studio / svn and edit features or scenarios.
We can get the pm’s to do it all in google docs, and then we can copy and paste them into feature files, but this will be error prone and will get out of sync very quickly.
What is the best practice for managing this?
Product owners or business analysts should, in general, not be writing features on their own, as this can lead to poorly structured, untestable scenarios.
A common approach is known as ‘the three amigos’ – a business stakeholder, developer and tester working together to write scenarios.
It’s fine to use Google Docs for the initial draft, but after that the features should be stored in version control, and the PO/BA should collaborate with a developer who has source control access on making changes.
You should make the version-controlled feature files easily accessible for review and reference to business stakeholders by linking to them from your intranet or wiki, or using a tool such as Relish.