Testing pyramid

Q: How deeply does Build Financial Software with Generative AI (From Scratch) cover testing pyramid?

Defines major layers and their trade-offs, but defers additional testing categories and fuller breakdowns.

As explained in Build Financial Software with Generative AI (From Scratch)

A testing pyramid is a model that organizes software tests by scope, with numerous fast isolated tests at the base and fewer slower broader tests toward the top.

The testing pyramid organizes tests by scope. Build many fast, isolated unit tests at the base, then add fewer broader tests as they become slower, less isolated, and more fragile. section 4.3.1

Move upward as tests involve more of the application:

Unit tests exercise code at the base and support frequent development, including test-driven development. section 4.3.1
Component tests isolate an API or similar component to find malformed requests and exception cases. section 4.3.1
Integration tests check whether multiple components work together despite their additional dependencies. section 4.3.1
UI tests automate user-like workflows, while manual and exploratory testing searches for broken behavior and interface inconsistencies. section 4.3.1

Testing a files endpoint

A FastAPI TestClient calls GET /files, then asserts a 200 status and the expected JSON response. A BDD version expresses the same behavior as a feature and step definitions.

How Build Financial Software with Generative AI (From Scratch) covers it

Cover of Build Financial Software with Generative AI (From Scratch)

liveBook manning.com

Read Build Financial Software with Generative AI (From Scratch) on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Unit Testing Principles, Practices, and PatternsThe Test Pyramid is a testing strategy that recommends a relative distribution of unit, integration, and end-to-end tests, with more tests in lower layers.
liveBook manning.com

Contract Testing in ActionThe test automation pyramid is a model that recommends distributing automated tests across unit, integration, and end-to-end layers, with fewer tests at slower and more expensive higher layers.
liveBook manning.com

Shipping Go: Develop, deliver, discuss, design, and go againA testing pyramid is a testing strategy with many fast unit tests at the base and progressively fewer broader, more expensive tests above them.
liveBook manning.com

Django in ActionA testing pyramid is a model that organizes software tests into levels based on scope, speed, and execution cost.
liveBook manning.com

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and TerraformThe testing pyramid is a model that organizes tests into layers, with broader and generally slower tests placed above narrower and generally faster tests.
liveBook manning.com

Think Like a Software Engineering ManagerThe testing pyramid is a test-suite design framework that emphasizes an appropriate distribution of automated tests across testing levels.
liveBook manning.com

gRPC Microservices in GoThe testing pyramid is a test-distribution model that places isolated unit tests below integration tests and end-to-end tests, with progressively fewer tests and greater execution cost at higher levels.

Compare how 8 books explain testing pyramid →

Related concepts

testhas part · A test is a procedure or check that evaluates behavior using specified inputs or evidence against expected results or criteria.
integration testhas part · An integration test evaluates whether multiple software components, or a component and an external dependency, interact and behave correctly together.
end-to-end testinghas part · End-to-end testing evaluates a complete system workflow across integrated components, from an external or user-relevant input to an observable outcome.
unit testhas part · A unit test is a test that evaluates the behavior of a small, isolated unit of software against expected behavior.
acceptance testinghas part · Acceptance testing evaluates whether a system or software satisfies specified user, business, or other stakeholder requirements and is acceptable for its intended purpose.

This explainer was generated by Manning's knowledge graph from the text of Build Financial Software with Generative AI (From Scratch). The section links point to the parts of the book it draws on.