Automated testing
Automated testing is the execution and evaluation of software tests by programs or tools rather than by manually performing each test procedure.
Test Driven: Practical TDD and Acceptance TDD for Java Developers
An automated test is a software test executed by a computer according to predefined instructions rather than performed manually.
- How it is used
- Protects evolving software against regression through repeatable tests and failure alerts.
- How deep it goes
- Explains harness qualities and testing workflows, without detailing test implementation.
- Examples
- Illustrates a test harness as a mold and a team running local test subsets before a server runs the full suite.
- What you can do after
- Evaluate how automated regression tests and human testing complement each other.
The Cloud at Your Service: The when, how, and why of enterprise cloud computing
The use of software to execute tests and check results with reduced human intervention.
- How it is used
- Uses cloud infrastructure and services to accelerate automated tests, especially when testing demand comes in bursts.
- How deep it goes
- Outlines unit, functional, visual, and load testing, then discusses cloud acceleration without detailing implementation.
- Examples
- Names JUnit and NUnit for automated unit tests and describes parallel testing with cloud servers.
- What you can do after
- Evaluate cloud options for accelerating tests and recognize the need to deploy and tear down environments quickly.
Effective Behavior-Driven Development
The execution of software tests by programmed tools or scripts rather than manually.
- How it is used
- Turns formulated BDD scenarios into executable tests that guide implementation and verify behavior.
- How deep it goes
- Details how scenario tools invoke team-written automation code and follows a red-green-refactor cycle without specifying tool internals.
- Examples
- Uses a collected-order scenario and a failing-to-passing scenario cycle.
- What you can do after
- Diagnose regressions by using failing tests to distinguish requirement contradictions from implementation defects.
Read how Effective Behavior-Driven Development explains automated testing →
Software Architecture Decision-Making
An automated test is an executable check that evaluates software behavior without requiring manual execution of the check.
- How it is used
- Uses executable checks to balance delivery speed against risk in critical paths, maintenance work, and changes that need repeatable feedback.
- How deep it goes
- Frames testing as a risk countermeasure and decision trade-off, but stops short of implementation techniques, test design, or tooling.
- Examples
- Uses one-off changes, critical user paths, dependency updates, package bumps, and framework upgrades as testing decisions.
- What you can do after
- Evaluate when automation is worth its delivery cost and identify risks that require tests, observability, rollback, or explicit ownership.
Read how Software Architecture Decision-Making explains automated testing →
Also covered in
- Microservices Patterns, Second EditionIn early access (MEAP)
- Building Reliable AI Systems
- Vibe EngineeringIn early access (MEAP)
- Claude at WorkIn early access (MEAP)
- Build High Value Software SystemsIn early access (MEAP)
- Spring Start Here, Second EditionIn early access (MEAP)
- Building Distributed Applications that Work
- Prompt Engineering in Practice
What to know first
- contractA contract is an agreed specification of the conditions, expectations, rights, or obligations that govern behavior or interactions between parties or software components.
- manual testingManual 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.
- test-driven developmentTest-driven development is a software development practice in which tests specify expected behavior and guide incremental implementation, typically being written before the corresponding code.
- test environmentA test environment is a configured computing context, including relevant software, hardware, data, and settings, in which software is executed and evaluated.
Related concepts
- integration testincludes · An integration test evaluates whether multiple software components, or a component and an external dependency, interact and behave correctly together.
- learning testincludes · A learning test is an automated test that verifies assumptions about code and teaches how that code behaves.
- scenario automation toolproduced by · A software tool that converts behavioral scenarios into executable tests by invoking automation code for their steps.
- manual testingcontrasts with · 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.
- test-driven developmentused by · Test-driven development is a software development practice in which tests specify expected behavior and guide incremental implementation, typically being written before the corresponding code.
- automationproduced by · Automation is the execution of tasks or processes by machines or software with reduced direct human intervention.
Questions about automated testing
What is automated testing?
Automated testing is the execution and evaluation of software tests by programs or tools rather than by manually performing each test procedure.
Which Manning books explain automated testing?
Test Driven: Practical TDD and Acceptance TDD for Java Developers, The Cloud at Your Service: The when, how, and why of enterprise cloud computing, Effective Behavior-Driven Development and Software Architecture Decision-Making.
What should I know before learning automated testing?
Manning books that teach automated testing usually introduce contract, manual testing, test-driven development and test environment first.
What is the difference between automated testing and manual testing?
Automated testing is the execution and evaluation of software tests by programs or tools rather than by manually performing each test procedure. 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.
What kinds of automated testing are there?
Kinds of automated testing include integration test and learning test.
What is automated testing also called?
Automated testing is also called automated tests or test automation.
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.



