Glue code in Behavior Testing Framework

One of the goals of Behavior Testing Framework is to create a strong separation between the business description of behaviors and the implementation details for those behaviors. This provides flexibility because you can change a scenario without having to worry about the implementation details, and you can change implementations without having to worry about the impact on scenarios.

However, this separation comes with a question. How can each scenario be associated with the correct implementation code? For example, when there is a step such as "Given I am a user with the "X" role", how does Behavior Testing Framework identify the correct impl method to execute?


How are steps in the business layer mapped to their implementations in the context implementation layer?

Behavior Testing Framework answers this question with the resource in the mapping layer. These are also referred to as the glue code, which means this code exists to connect different sets of code that are otherwise incompatible.

There are three types of resources that form the glue code:

  • Context Factory
  • RemoteSmokeTestHelperModule
  • The step methods