Understand BDD thoroughly, (StoryBDD, SpecBDD)?

Question

PHP

Hello dear colleagues, please help me understand BDD to the end, for example, let's take behat and phpspec .
Suppose we start a new project in which we have 10 features (features), we immediately describe them for tests (StoryBDD) in behat and start implementing them according to the specifications through phpspec (SpecBDD). All this, of course, in the ideal mode as conceived by the authors.
The question arises, what if the features are not 10, but 100? Is it worth it to divide into iterations, let's say 10 each (I can't fully understand the ideology of BDD)?
The first schema looks like this:
100 features -> StoryBDD(behat) -> SpecBDD(phpspec) -> done
Second:
100 features ->
10 features -> StoryBDD(behat) -> SpecBDD(phpspec) ->
...
10 features -> StoryBDD(behat) -> SpecBDD(phpspec) ->
done
And what if we decided to add another one while developing feature 25? Do we do it immediately after the end of the current one, or do we move it behind the last one?
Please share your experience!
Thank you!

Answer 1

And what does BDD have to do with the number of iterations in a sprint, or something like that? Its meaning is quite simple, write a story --> write a test --> check that the test is red --> write the code, the minimum required --> check that the test is green --> refactoring. Next is the next feature.