liveBook · Manning

Integration test

As explained in Secure APIs

An integration test verifies that multiple software components work together as intended.

An integration test verifies that multiple software components work together as intended. For APIs, it checks that the implemented server follows the design, exposes expected behavior, and remains secure and robust. section 1.5

An API integration-test suite can:

  • Validate expected API behavior. section 1.5
  • Simulate user flows across the API. section 1.5
  • Run alongside fuzz testing and API security testing, which check specification compliance and security. section 1.5
Figure 1.6 Security by design fits into every step of the API development cycle. It encourages us to approach design, implementation, testing, and operations from a security point of view.
figure

Use the API development-cycle figure to place integration testing after implementation and alongside broader security checks. section 1.5

How Secure APIs covers it

How deep it goes
Defines a suite-level testing role but does not specify individual test cases, code, or implementation internals.
Examples
Uses expected API behavior checks and simulated user flows as concrete test targets.
What it assumes
Assumes an implemented API and an API design whose expected behavior can be tested.
What you can do after
Apply it by building integration-test suites that validate API behavior and simulate user flows.
How it connects
Connects API design compliance with fuzz testing, API security testing, CI/CD, and monitoring.

Also explained in

Compare how 31 books explain integration test →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Secure APIs. The section links point to the parts of the book it draws on.