Feature
: Behavior Driven Development (BDD).
In order to
:- Avoid rework due to misunderstand and slow feedback among project manager, project owner, developer, QA/tester, sales, any guys join IT projects and customer.
And
make project information is transperant as human readable.And
keep software functions work as design after refactor/restructure code.
As
people (tech/non-tech)want to
get knowledge of BDD.Scenario
: BDD OverviewGiven
: knowledge of Test Driven Development TDD.When
:- Break out user story to one or many features that cover one minimum aspect of story.
And
split out a feature to set of details secnarios that each scenario has limited scope with explicit input and output.
Then
software engineer(dev/test/QA/DevOps) use standard keyword syntax in human readable to write a test case, that is over on top of application function interface, covers scenario description.