Behavior-Driven Development (BDD) makes it clear that you need to establish a language that describes the problems you are aiming to fix. Whether you use an internal DSL (built on top of your programming language) or an external DSL like Gherkin, Dave suggests a four-layer approach to test code. These layers include: the test cases, which focus on what the system needs to do; the DSL layer, which defines the language and provides helpful tools; and the protocol drivers, which act as the "glue" that translates ideas in the problem domain's language into interactions with the system under test.

-

#softwareengineering #softwaredevelopment #programming

Continuous Delivery

A four-layer architectural approach to structuring test code is presented, centered around BDD principles. The layers consist of: test cases focused on system behavior, a DSL layer that defines the language used in those tests, and protocol drivers that translate domain language into interactions with the system under test. The approach works for both internal DSLs built on top of a programming language and external DSLs like Gherkin. The core idea is to consciously build a domain-specific language that makes writing and implementing BDD scenarios easier and more consistent.

The 4 Layer Approach to Your Test Code