Manual testing
Manual testing is the evaluation of software by a person who performs test actions and assesses the resulting behavior rather than relying on automated test execution.
Acing the Frontend Interview
Manual testing is the evaluation of software by a person executing test scenarios and judging the resulting behavior or presentation.
- How it is used
- Applies human judgment to exploratory, usability, accessibility, and edge-case evaluation.
- How deep it goes
- Explains benefits, limitations, and strategic complementarity but stops short of prescribing a detailed manual test procedure.
- Examples
- Uses visual layout, accessibility, unexpected edge cases, complex UI states, and integrations as evaluation targets.
- What you can do after
- Evaluate when human testing adds value and explain how to balance it with automated testing.
Read how Acing the Frontend Interview explains manual testing →
The Cloud at Your Service: The when, how, and why of enterprise cloud computing
Software testing in which people evaluate software by carrying out test activities without relying solely on automated execution.
- How it is used
- Uses manual testing to address uneven QA workloads and augment teams with short bursts of crowdsourced capacity.
- How deep it goes
- Explains workload trade-offs and worker limitations, but does not provide a detailed testing procedure.
- Examples
- Illustrates a regional website access check and visual inspection across major browsers.
- What you can do after
- Apply crowdsourced manual testing through Amazon Mechanical Turk to suitable, bounded QA tasks.
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 →
Vibe Engineering
Manual testing is the evaluation of software behavior by a human executing and inspecting test procedures rather than automated test code.
- How it is used
- Uses brief exploratory execution to discover unknown behavior before designing automated tests for AI-generated code.
- How deep it goes
- Explains rationale, timing, happy-path and edge-case exploration, then stops short of treating manual testing as scalable verification.
- Examples
- Uses markup-heading inputs and UI migration with limited coverage as concrete cases for exploratory human checking.
- What you can do after
- Practice/perform focused exploration, recognize unexpected behavior, and turn observations into stronger automated tests.
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.
Also covered in
- Think Like a CTO
- Architecting AccessibilityIn early access (MEAP)
- Practices of the Python Pro
- gRPC Microservices in Go
- Learn PowerShell Scripting in a Month of Lunches, Second Edition: Write and organize scripts and tools
- Build Python Web Apps with Streamlit
What to know first
- automationAutomation is the execution of tasks or processes by machines or software with reduced direct human intervention.
- bugA software bug is a defect that can cause software to behave incorrectly or differently from its intended or specified behavior.
- microservice architectureMicroservice architecture is a software architectural style that structures an application as independently deployable services, typically organized around focused capabilities and communicating through defined interfaces.
- software testingSoftware testing is the systematic evaluation of software under specified inputs or conditions to assess its behavior against expected results or requirements and identify defects.
Related concepts
- software testingkind of · Software testing is the systematic evaluation of software under specified inputs or conditions to assess its behavior against expected results or requirements and identify defects.
- automated testingcontrasts with · Automated testing is the execution and evaluation of software tests by programs or tools rather than by manually performing each test procedure.
- browser developer toolsuses · Browser developer tools are browser-integrated utilities for inspecting, debugging, testing, profiling, and analyzing web pages, applications, and browser-executed code.
- quality assuranceused by · Quality assurance is a systematic set of activities for evaluating and improving products or processes to ensure they meet defined quality requirements.
- acceptance testingcontrasts with · Acceptance testing evaluates whether a system satisfies specified user, business, or stakeholder requirements and acceptance criteria.
Questions about manual testing
What is manual testing?
Manual testing is the evaluation of software by a person who performs test actions and assesses the resulting behavior rather than relying on automated test execution.
Which Manning books explain manual testing?
Acing the Frontend Interview, The Cloud at Your Service: The when, how, and why of enterprise cloud computing, Lead Developer Career Guide, Vibe Engineering and Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform.
What should I know before learning manual testing?
Manning books that teach manual testing usually introduce automation, bug, microservice architecture and software testing first.
What is the difference between manual testing and automated testing?
Manual testing is the evaluation of software by a person who performs test actions and assesses the resulting behavior rather than relying on automated test execution. Automated testing is the execution and evaluation of software tests by programs or tools rather than by manually performing each test procedure.
What is manual testing a kind of?
Manual testing is a kind of software testing. Software testing is the systematic evaluation of software under specified inputs or conditions to assess its behavior against expected results or requirements and identify defects.
What is manual testing also called?
Manual testing is also called manual tests.
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.




