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.
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
Updated docs #3047
Updated docs #3047
Conversation
* implement each step of a scenario for testing | ||
* write actual code implementing the feature | ||
|
||
By making every feature to be formally written (in User Story format) and test automated, we ensure that business, developers, QAs, managers are in the same boat. That everyone in a team knows what is developed, what is not, what is tested and what is not. By making tests to be a part of user story BDD allows that non-technical personnel to write (or edit) acceptance tests. BDD also encourages exploration and discussions. To formalize the requirements and write user story in a way everyone can understand them, business and developers should talk, ask questions, and play the scenarios of features to implement. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... and play
the scenarios of features to implement.
I'm not sure to understand the word "play" in this sentence.
I'm not sure if it sounds better or not but I found the original text a bit hard to understand.
Added a doubt: #3072 |
sent #3103 |
@@ -85,7 +85,7 @@ class Configuration | |||
'settings' => [ | |||
'colors' => false, | |||
'bootstrap' => false, | |||
'strict_xml' => false, | |||
'strict_xml' => true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
accidentally added to commit
Includes BDD documentation. And more to come.
Please review, leave comments. If you see mistakes - please fix them (it is easy to open and edit file and submit pull request)