System under test
A system under test is the component or system whose behavior is exercised and evaluated by a test.
Unit Testing Principles, Practices, and Patterns
The system under test is the class, component, or larger unit whose behavior a test exercises and verifies.
- How it is used
- Frames unit-test boundaries and clarifies which behavior or code is being verified.
- How deep it goes
- Contrasts class-centered and behavior-centered boundaries, then demonstrates each with collaborator-isolation examples.
- Examples
- Uses customer purchases, store inventory, mocks, and interaction verification to contrast classical and London-style tests.
- What you can do after
- Evaluate whether a test verifies meaningful behavior or over-specifies the SUT's implementation and collaborator interactions.
Read how Unit Testing Principles, Practices, and Patterns explains system under test →
The Art of Unit Testing 3e
A system under test is the subject, system, suite, component, class, or code being tested.
- How it is used
- Identifies the code or system a test exercises and checks.
- How deep it goes
- Defines the SUT and expands a unit beyond one function to entry-to-exit work, without detailing internals.
- Examples
- Uses a sum function test and a password-verification test named for its scenario and expected result.
- What you can do after
- Evaluate what a test exercises and identify its scenario and expected behavior from a clear test name.
Read how The Art of Unit Testing 3e explains system under test →
Testing Spring Boot Applications
The application under test is the software system whose behavior is being verified by a test.
- How it is used
- Anchors decisions about which application components and external interactions a test verifies.
- How deep it goes
- Defines the test subject and lifecycle, then stops short of prescribing one universal context size.
- Examples
- Uses a weather dashboard, Open-Meteo integration, local fake API, controller, repositories, and application architecture.
- What you can do after
- Operate/configure a Spring Boot application context and select suitable real, stubbed, or mocked dependencies for tests.
Read how Testing Spring Boot Applications explains system under test →
gRPC Microservices in Go
A system under test is the software element whose behavior is being evaluated, ranging from a class or layer to an entire application.
- How it is used
- Identifies the exact software element targeted by a test, from a class or layer to a service or entire application.
- How deep it goes
- Defines scope and test phases, then stops short of prescribing one testing strategy or dependency setup.
- Examples
- Uses Fibonacci testing, an Order service, MySQL dependencies, test containers, and mocked PaymentPort and DBPort interfaces.
- What you can do after
- Evaluate/understand behavior by isolating a target, controlling dependencies, and verifying expected results across test scenarios.
Read how gRPC Microservices in Go explains system under test →
Shipping Go: Develop, deliver, discuss, design, and go again
A system under test is the bounded software unit whose behavior is evaluated by a test.
- How it is used
- Structures testing around bounded units whose inputs and outputs can be evaluated independently.
- How deep it goes
- Defines black-box boundaries and identifies service, handler, and server roles, but does not descend into testing internals.
- Examples
- Uses a Go translation service, HTTP handler, server, and given-when-then translation scenario.
- What you can do after
- Build testable service, handler, and server boundaries, then evaluate behavior through inputs and expected outputs.
Read how Shipping Go: Develop, deliver, discuss, design, and go again explains system under test →
Also covered in
What to know first
- exceptionAn exception is a runtime signal or value representing an abnormal condition that interrupts ordinary program flow and can be handled or propagated.
- integration testAn integration test evaluates whether multiple software components, or a component and an external dependency, interact and behave correctly together.
Related concepts
- automation solutionused by · An automation solution is a supporting system that integrates automated tests, execution frameworks, libraries, environments, and glue code to verify another system’s behavior.
- Fit fixtureused by · A Fit fixture is a class that interprets a table-based test and connects it to the software being tested.
- Spring Boot testconfigured by · Spring Boot testing support provides facilities for testing application code with Spring-managed components, configuration, and framework behavior.
- @SpringBootTestconfigured by · @SpringBootTest is a Spring Boot testing annotation that loads an application context with Spring Boot support for integration testing.
- software testingused by · 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.
- test suiteused by · A test suite is an organized collection of tests that can be executed together to assess a software system or model against specified behaviors or criteria.
Questions about system under test
What is system under test?
A system under test is the component or system whose behavior is exercised and evaluated by a test.
Which Manning books explain system under test?
Unit Testing Principles, Practices, and Patterns, The Art of Unit Testing 3e, Testing Spring Boot Applications, gRPC Microservices in Go and Shipping Go: Develop, deliver, discuss, design, and go again.
What should I know before learning system under test?
Manning books that teach system under test usually introduce exception and integration test first.
What is system under test also called?
System under test is also called SUT or application under test.
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.




