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.
- Andmake project information is transperant as human readable.
- Andkeep software functions work as design after refactor/restructure code.
 
- Aspeople (tech/non-tech)- want toget knowledge of BDD.
- Scenario: BDD Overview- Given: knowledge of Test Driven Development TDD.
- When:- Break out user story to one or many features that cover one minimum aspect of story.
- Andsplit out a feature to set of details secnarios that each scenario has limited scope with explicit input and output.
 
- Thensoftware 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.