Is BDD really applicable at the UI layer?

Question

BDD is an \"outside-in\" methodology, which as I understand it, means you start with what you know. You write your stories and scenarios, and then implement th

Answer 1

What does the BDD is describing?

In teams following a Behaviour Driven Development (BDD), the Acceptance Criteria (aka Rules) should describe "what the system does" instead of "how the system does it".

So, where are the UI/UX details are captured in a team which is following BDD?

In teams using BDD, The User Interface (UI) and User Experience (UX) (buttons, clicks, animations, etc) layer details should not be included as an Acceptance Criteria (aka Rules) in text format, under a ticket (e.g. issued with a Software Ticketing Tool such as JIRA, GitLab, etc). Instead they should be included within the design screens (wireframes, user journey, individual screens etc). For example, text notes may be embedded on the design screens with annotations, or just as comments next to the screens.