These are chat archives for Behat/Behat

4th
Oct 2016
Roel Monnens
@roelmonnens
Oct 04 2016 06:46
Hello, I’m trying to get BDD going in my company. What we do is, we’re letting the PO write the features. Then we have a meeting in which we write the scenarios together with the PO and save this feature-file in our git repo. Now this works for the developers. They can see the feature file but the PO has no access to our git-repo. We don’t want to keep a copy of the feature-file because that’s double the work and we actually don’t want to give the PO access to the git-repo. Does anybody have experience with this problem? And how did you solved this?
Ciaran McNulty
@ciaranmcnulty
Oct 04 2016 11:18
Does it need to be a .feature in perfect Gherkin syntax at that stage?
I find it useful to only put these things in git as they're being implemented
We keep scenarios in Jira and transfer them to git as the feature is built - this means the features in the repo reflect the actual application
Roel Monnens
@roelmonnens
Oct 04 2016 11:23
but after you transfer them to git. Do you also keep a copy in Jira?
Ciaran McNulty
@ciaranmcnulty
Oct 04 2016 11:23
In the sense that we keep old User Stories, but we rarely look at them
User Stories are like diffs, Features are like the current state
Are you talking about being able to browse the features after implementation then? There are some tools for that
Roel Monnens
@roelmonnens
Oct 04 2016 11:24
Yep that’s what I’m talking about
Ciaran McNulty
@ciaranmcnulty
Oct 04 2016 11:25
I don't use any so can't recommend. I think Pickles Pro does - I know Cucumber Pro is all about this
Roel Monnens
@roelmonnens
Oct 04 2016 11:25
the PO want to see the features after implementation before he start Version 2 of this part of the system
k thnx will look into those
Ciaran McNulty
@ciaranmcnulty
Oct 04 2016 11:28
There may be some open tools for it too