The evaluation of software behavior by a person executing test steps rather than by an automated test program.
Manual testing evaluates software behavior through human execution of test steps, often by running the application and visually inspecting its output. It provides a practical starting point for prototypes and minimum viable products before automated testing justifies its infrastructure cost. section 9.0
Make manual testing efficient enough for early development:
Start the application from a clean development computer with a short, repeatable script. section 12.8
Use Docker Compose to run the application and database fixtures in a testable local state. section 12.8
Run the code, inspect its output, and repeat the necessary checks while the product is still changing rapidly. section 9.0
Replace repetitive manual checks with automated testing when they become tedious, time-consuming, or too burdensome for the team. section 9.0
Testing an early microservices MVP
A startup can use a startup script, Docker Compose, and database fixtures to bring its MVP from an empty development computer to a testable state, then verify behavior manually. This is adequate while the product is being proved; as the application grows, repetitive checks should move to automated tests. section 12.8section 9.0
How Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform covers it
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 it assumes
Assumes a runnable application and development environment, while treating automated testing as a later skill.
What you can do after
Apply manual checks efficiently during early development and recognize when repetitive testing should become automated.
How it connects
Connects manual testing with automated testing, microservices, Docker Compose, database fixtures, and MVP development.
testkind of · A test is a procedure or check that evaluates behavior using specified inputs or evidence against expected results or criteria.
quality assuranceused by · Quality assurance is the planned, systematic evaluation and improvement of products or processes to prevent or detect defects and ensure they meet defined quality requirements.
browser developer toolsuses · A suite of browser-integrated utilities for inspecting, debugging, testing, profiling, and analyzing web pages, applications, and browser-executed code.
acceptance testingcontrasts with · Acceptance testing evaluates whether a system or software satisfies specified user, business, or other stakeholder requirements and is acceptable for its intended purpose.
pipelinealternative to · A pipeline is an ordered or coordinated sequence of connected processing stages or tasks that passes data, work, or results toward an outcome.
This explainer was generated by Manning's knowledge graph from the text of Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform. The section links point to the parts of the book it draws on.
