I am involved in a project where Given-When-Then formatted stories are written by the Product Owner (in a web-based story repository / JIRA), then created by Developers, while system test automation (written as SpecFlow .feature files) is built by the Tester to cover all testable behaviours.
What seems to happen as a natural part of the lifecycle is that the test automation logic will combine, extend and clarify the details of the original acceptance criteria. This further definition can be lost, however, since the .feature files are only reviewed by the Tester, while the Product Owner wants only to be exposed to the original set of stories and acceptance criteria.
It seems like we might be breaking BDD by not exposing the .feature files to the Product Owner, but even if the latest .feature files are available through a version control tool, does that mean our Product Owner would need to learn about that as well?
And even if they access these files through version control, how are Product Owners supposed to write useful GWT statements without also using the IDE to discover/intellisense the existing step definitions?
What experiences are others having with this type of situation? Any suggestions are appreciated.