Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Behaviour driven development #22

Open
MikeSmithEU opened this issue Feb 7, 2019 · 2 comments
Open

Behaviour driven development #22

MikeSmithEU opened this issue Feb 7, 2019 · 2 comments
Labels
workflow

Comments

@MikeSmithEU
Copy link
Contributor

(related to #14 and #21 )

It seems like it would be a good idea, but needs some enthusiasm from all parties involved, developers and analysts/stakeholders.
If developers are willing to aid analysts in writing correctly formatted specifications in the dialect of the chosen BDD, and implement these, and equally the analysts are willing to learn and keep to the newly learned BDD dialect, then it could increase our overall efficiency, as well as create clarity to the proceedings.
@MikeSmithEU MikeSmithEU added the for discussion Further information is requested label Feb 7, 2019
@MikeSmithEU MikeSmithEU mentioned this issue Feb 22, 2019
Closed
@EyalLavi
Copy link
Contributor

EyalLavi commented Mar 1, 2019

Speaking for the "analysts" I'm completely in favour and willing to adapt to whatever dialect we choose. I have experience of Cucumber.

@EyalLavi
Copy link
Contributor

Action before closing: add BDD for release 1.

@EyalLavi EyalLavi removed the for discussion Further information is requested label May 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
workflow
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MikeSmithEU @EyalLavi