Following on from my previous question and the comments under the accepted answer: One Acceptance Test project per layer or one Acceptance Test project per Bounded Context
I have done a lot of reading into BDD recently as I try to decide whether it is applicable to a project. I have come across the term Honeycomb (https://skillsmatter.com/skillscasts/10933-sub-second-tdd-with-a-dash-of-honey), which seem to suggest that "end to end" can mean different things depending on whether you are interested in speed or reliability. In one case it may mean the UI (most outer layer) to the Domain Model (most inner layer) and in another case it may just mean the domain model on its own. I cannot find any more information about Honeycomb.
Have I understood "end to end" correctly? My team is currently developing a Domain Model for an application. We will not be writing the other layers e.g. application service; UI etc. Is it normal to use BDD to test one layer of the application in isolation? i.e. in this case end to end is from Domain Model to Domain Model rather than UI to Domain Model.
The reason I ask is because I believe it will help us to engage with business analysts and QA. However, I don't want to abuse BDD.