Code coverage

Q: How deeply does Think Like a Software Engineering Manager cover code coverage?

Defines line, branch, and method coverage and explains benefits and limits, without detailing calculations or tooling.

As explained in Think Like a Software Engineering Manager

The proportion of source code or execution paths exercised by automated tests.

Code coverage indicates how much code or which execution paths tests exercise. It can help identify defects early and give developers confidence, but high coverage does not guarantee bug-free software. section 12.2.2

Coverage metrics can track:

Line coverage: whether code lines are exercised. section 12.2.2
Branch coverage: whether execution paths are exercised. section 12.2.2
Method coverage: whether methods are exercised. section 12.2.2

Use coverage as a signal

An engineering manager can monitor coverage to track progress and spot areas for improvement or potential problems. Consider it alongside other indicators of service and codebase health. section 1.2.4 section 12.2.2

How Think Like a Software Engineering Manager covers it

Cover of Think Like a Software Engineering Manager

liveBook manning.com

Read Think Like a Software Engineering Manager on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Unit Testing Principles, Practices, and PatternsThe ratio of production-code lines executed by at least one test to the total number of production-code lines.
liveBook manning.com

Shipping Go: Develop, deliver, discuss, design, and go againTest coverage is a measure of how much of a system's code or behavior is exercised by tests.
liveBook manning.com

Effective Platform EngineeringTest coverage is the proportion of specified code, paths, branches, or behaviors exercised by automated tests.
liveBook manning.com

Go in Practice, Second EditionCode coverage is a measurement of which portions of program code are executed by a test suite.
liveBook manning.com

Functional Programming in JavaScriptThe proportion of a program’s executable code that is exercised by a test suite or other execution run.
liveBook manning.com

100 Java Mistakes and How to Avoid ThemCode coverage is the fraction of program code elements executed during a test suite.
liveBook manning.com

gRPC Microservices in GoCode coverage is a metric indicating the proportion of source-code elements exercised by a set of tests.
liveBook manning.com

Architecture Modernization: Socio-technical alignment of software, strategy, and structureTest coverage is a measure of how much of a codebase's behavior or structure is exercised by automated tests.
liveBook manning.com

"Looks Good to Me"A measure of the proportion of source code elements or execution paths exercised by tests.
liveBook manning.com

Learn Go with Pocket-Sized ProjectsCode coverage is the percentage or proportion of program code executed by a test suite.
liveBook manning.com

Go in Action, Second EditionCode coverage is a measurement of which portions or execution paths of a program are exercised by tests.
liveBook manning.com

The Art of CodeTest coverage is a measure of how much software code or behavior is exercised by automated tests.
liveBook manning.com

AI-Powered Developer: Build software with ChatGPT and CopilotCode coverage is the proportion of a program’s code executed when a specified test suite runs, usually expressed as a percentage.

Compare how 14 books explain code coverage →

Related concepts

branch coverageincludes · Branch coverage is a test coverage metric measuring the proportion of a program’s control-flow branches executed by tests.
testmeasures · A test is a procedure or check that evaluates behavior using specified inputs or evidence against expected results or criteria.
evaluation suitemeasures · An evaluation suite is an organized collection of tests, cases, or tasks used to assess a system against specified behaviors or criteria.
go testmeasured by · go test is the Go command that builds and runs tests for specified packages and can also execute benchmarks and report coverage.

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.