liveBook · Manning

Manual testing

Manual testing is the evaluation of software by a person who performs test actions and inspects the resulting behavior rather than relying on automated test execution.

How 2 Manning books explain it

Lead Developer Career Guide

Testing performed by a person who evaluates software behavior without relying entirely on automated test execution.

How it is used
Uses human evaluation alongside automated checks to assess software quality and user experience.
How deep it goes
Defines the role and places it within documented QA stages, but stops short of detailed test procedures.
Examples
Uses an e-commerce QA process and checks whether design and user experience match requirements.
What you can do after
Apply it alongside unit and integration testing to evaluate user experience and broaden software quality coverage.

Read how Lead Developer Career Guide explains manual testing →

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

The evaluation of software behavior by a person executing test steps rather than by an automated test program.

How it is used
Supports early validation of prototypes and MVPs before investing in automated testing infrastructure.
How deep it goes
Explains visual inspection and repeatable local setup, but stops short of defining detailed test procedures or coverage.
Examples
Uses local application execution, visual output inspection, startup scripts, Docker Compose, and database fixtures.
What you can do after
Apply manual checks efficiently during early development and recognize when repetitive testing should become automated.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains manual testing →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.