Integration layer

As explained in BDD in Action, Second Edition

An integration layer is the architectural layer of a test automation system that translates domain activities into low-level interactions with external system interfaces and manages their clients.

The integration layer bridges business activities and technology interfaces. It translates domain-level actor activities into exact interactions with the system under test and manages the clients that perform them, such as HTTP clients and web browser drivers. section 14.4 section 15.2

Typical integration-layer responsibilities include:

• Connecting domain activities to web interfaces, mobile applications, and programmatic APIs such as REST or GraphQL. section 15.2
• Identifying interactable elements, setting up test data, producing test reports, and integrating with test tools. section 14.2.1
• Integrating with the test execution environment, test infrastructure, and the people and processes that run tests and analyze results. section 15.2

Keep low-level interactions out of specifications

A maintainable test keeps business-facing workflow steps in the Specification and Domain layers, then delegates browser-driver or HTTP-client details to the integration layer. Calling Selenium WebDriver APIs directly from a specification couples the workflow to a specific interface and tool, making later techniques such as blended testing harder to introduce. section 14.2.1 section 14.4

Figure 14.15 Layers of a typical test automation system based on Serenity/JS, with their contents

Use the layer diagram to locate the integration layer beneath the Domain and Specification layers and see the technologies and responsibilities assigned to it. section 14.2.1

How BDD in Action, Second Edition covers it

How deep it goes

Defines responsibilities and architectural boundaries, including low-level interaction translation, client management, test data, and reporting.

Examples

Uses HTTP clients, web browser drivers, web interfaces, mobile apps, REST APIs, GraphQL APIs, test data, and reports.

What you can do after

Apply it by isolating interface-specific interactions and clients beneath domain-level workflow abstractions.

How it connects

Connects the Domain layer with the Specification layer, external interfaces, test tools, test data, reporting, and execution environments.

liveBookmanning.com

Read BDD in Action, Second Edition on liveBook Get the book at manning.com

Related concepts

• multi-tier applicationpart of · A multi-tier application is an application organized into distinct tiers that separate responsibilities and interact through defined dependencies or interfaces.
• system under testuses · A system under test is the software, hardware, component, configuration, or other subject whose behavior is exercised and evaluated by testing.
• automation solutionpart of · An automation solution is a supporting system that integrates automated tests, execution frameworks, libraries, environments, and glue code to verify another system’s behavior.
• interfaceuses · A software interface is a contract or boundary that specifies the operations, properties, or capabilities through which types or components interact, without requiring a particular implementation.
• test environmentuses · A test environment is a configured computing context, including relevant software, infrastructure, data, and settings, in which software is tested.

This explainer was generated by Manning's knowledge graph from the text of BDD in Action, Second Edition. The section links point to the parts of the book it draws on.