liveBook · Manning

Unit test

As explained in Google Anthos in Action

Unit testing is the practice of testing an isolated software unit, such as a function, class, or module, against expected behavior.

A unit test checks an isolated software unit, such as a function, class, module, or business-domain service, against expected behavior. In modernization work, continuous integration runs unit tests to provide rapid feedback and expose problems early. section 16.1

Unit testing supports modernization by:

  • Identifying and fixing application problems faster through automated checks in the build pipeline. section 16.1
  • Building and testing a single business-domain service in isolation after capabilities are decoupled into smaller services. section 16.1

How Google Anthos in Action covers it

How deep it goes
Defines isolated testing and its CI role, but stops short of detailing test design, execution mechanics, or assertion strategies.
Examples
Tests a decoupled business-domain service in isolation as part of an application build pipeline.
What you can do after
Apply unit tests through continuous integration to identify and fix application problems faster.
How it connects
Connects unit testing with continuous integration, service decomposition, automated integration testing, and user acceptance testing.

Also explained in

Compare how 9 books explain unit test →

Related concepts

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