Bdd development flow process from end to end
0 likes432 views
The document outlines the process of developing business requirements into stories, including drafting acceptance criteria in Gherkin format and elaborating on them through BDD scenarios. It emphasizes the collaborative roles of QA and developers in testing, scenario implementation, and automated testing via an existing framework. The workflow culminates in regression testing and deployment to production, ensuring that all BDD tests pass successfully before the story is marked as done.
Bdd development flow process from end to end
- 1. Requirements from Business PO creates story for business requirements with high level requirments BA creates draft acceptance criteria based on requirments in Gherkint Format with NO EXAMPLES QA Reviews the Acceptance criteria QA Elobrates the Acceptance Criteria and created BDD Scenarios If not clearIf not clear Adds EXAMPLES, POSTIVE NEGATIVE SCENARIOS, EDGE CASES STORY is presented in the sprint planning Effort estimation, Sprint velocity, Feasibilty to take to sprint? BDD by QA Yes Automated the BDD scenarios using existing Framework Modify scenarios to reuse existing steps. Implements Steps. Tests should fail with assertions Developer implments the story based on BDD Sceanrios No Feature Branch - Sudo test env is created with Developers code deployed Automated tests are run to check if all the scenarios implemented If BDD tests passed? Test Failed with Bug? Test Failed in automation Aprpove the story and Merge the code to Develop Branch Run Regression tests in Test Env on dev branch Regression test failed Failed Passed Move story to DONE Ready to go to Live and story in Production for end users BDD tests passed