This is the flow how a developer and SDET works in BDD and pushes every story to live. This included from and idea to live including automation in BDD.

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