liveBook · Manning

Cross-cutting concern

As explained in Effective Behavior-Driven Development

A concern, such as logging or timing, that affects multiple parts of a software system rather than one isolated operation.

When REST API driver methods each need extra logging and timing, duplicating that code becomes awkward to maintain. These are cross-cutting concerns: they affect multiple test actions rather than one isolated operation. A shared TestAction wrapper can handle them around each action. section 15.4

Login and registration actions

A driver can create login and registration actions, while step definitions call Execute(). Shared execution logic adds timing and logging without repeating it in each driver method. section 15.4

How Effective Behavior-Driven Development covers it

How deep it goes
Traces repeated logging and timing into shared TestAction execution, with derived-class and lambda-backed implementations.
Examples
Contrasts duplicated driver logging and timing with login and registration actions invoked from step definitions.
What you can do after
Apply the Test Action pattern to wrap driver actions with shared logging, timing, and exception handling.
How it connects
Connects cross-cutting concerns with test actions, REST API drivers, and step definitions.

Also explained in

Compare how 6 books explain cross-cutting concern →

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.