liveBook · Manning

Driver interface

As explained in Effective Behavior-Driven Development

A contract defining the actions and data exchange that automation code expects from a test driver, independently of the application interface used to perform them.

A driver interface defines the actions automation code needs and the data those actions accept and return. Because these needs can be independent of the application interface, multiple drivers can support the same logical scenario through different application interfaces. section 15.6

Authentication drivers

An authentication interface can define Login and Register actions. REST API and service drivers can implement that contract, letting scenarios use the same actions while the implementation varies. section 15.6 section 15.6

Figure 15.5 Polymorphic driver interface with multiple implementations

Use the diagram to see how one driver interface can connect to multiple implementations. section 15.6

How Effective Behavior-Driven Development covers it

How deep it goes
Defines actions and their data, then illustrates multiple implementations without detailing their full construction.
Examples
Uses authentication Login and Register actions with REST API and service driver implementations.
What it assumes
Assumes familiarity with BDD scenarios and the Test Driver and Test Action patterns.
What you can do after
Apply polymorphic drivers to reuse logical scenario actions across different application interfaces.
How it connects
Connects to the Test Driver pattern, the Test Action pattern, BDD scenarios, and polymorphic drivers.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Behavior-Driven Development. The section links point to the parts of the book it draws on.