liveBook · Manning

Acceptance testing

Also called acceptance test

Acceptance testing evaluates whether a system satisfies specified user, business, or stakeholder requirements and acceptance criteria.

How 5 Manning books explain it

BDD in Action, Second Edition

An acceptance test verifies that software satisfies agreed behavioral and business requirements.

How it is used
Checks agreed business-facing behavior while guiding implementation and showing whether delivered features meet acceptance criteria.
How deep it goes
Develops a workflow from collaborative examples through scenarios and automation, then addresses reliability and maintenance rather than stopping at a definition.
Examples
Uses a refined commuter-train scenario, frequent-flyer points requirements, and high-level tests retrofitted to legacy applications.
What you can do after
Build it from scratch by turning business-readable scenarios into automated checks, then use their results as feedback on implemented behavior.

Read how BDD in Action, Second Edition explains acceptance testing →

Test Driven: Practical TDD and Acceptance TDD for Java Developers

Acceptance testing is the process of checking whether a system satisfies conditions for acceptance by its stakeholders.

How it is used
Drives feature development with customer-owned acceptance criteria and supports collaboration around requirements.
How deep it goes
Explains the acceptance TDD cycle and compares implementation strategies, including interface-level and direct testing.
Examples
Contrasts invalid payment-card checks with a browser-based session-timeout redirect test.
What you can do after
Evaluate acceptance testing strategies against feature needs, expected change, and technology.

Read how Test Driven: Practical TDD and Acceptance TDD for Java Developers explains acceptance testing →

Think Like a Software Engineering Manager

User acceptance testing is testing performed by end users or stakeholders to determine whether software satisfies their requirements and is ready for deployment.

How it is used
Positions UAT as a user-perspective check of requirements and deployment readiness.
How deep it goes
Defines who tests and what they assess, but provides no UAT procedure or acceptance checklist.
Examples
Uses an employee beta release as a related example of gathering feedback and fixing bugs before customers receive software.
What you can do after
Evaluate/understand whether user or stakeholder testing addresses requirements and readiness for deployment.

Read how Think Like a Software Engineering Manager explains acceptance testing →

Vibe Engineering

A test that evaluates whether a system or feature satisfies product-level requirements from a user's or stakeholder's perspective.

How it is used
Uses acceptance tests as an independent product-requirements check on agent-generated business logic.
How deep it goes
Explains circular tests and prescribes a human-written or ticket-derived acceptance test for each agent-generated pull request touching business logic.
Examples
Uses a discount-rounding mismatch and a team’s pull-request requirement to illustrate specification violations and their detection.
What you can do after
Practice writing or deriving acceptance checks from requirements before trusting tests for agent-generated business logic.

Read how Vibe Engineering explains acceptance testing →

Django in Action

An acceptance test verifies that software satisfies requirements from the perspective of an expected feature or user outcome.

How it is used
Verifies that features satisfy requirements through behavior that matches intended user outcomes.
How deep it goes
Defines feature-level behavior and its place in the testing pyramid, but does not detail implementation procedures.
Examples
Uses a shipping-cost page with varied addresses and shipping zones to illustrate the cost of higher-level testing.
What you can do after
Evaluate whether a defined feature works as designed from a requirements-oriented, often user-facing perspective.

Read how Django in Action explains acceptance testing →

Also covered in

What to know first

Related concepts

Questions about acceptance testing

What is acceptance testing?

Acceptance testing evaluates whether a system satisfies specified user, business, or stakeholder requirements and acceptance criteria.

Which Manning books explain acceptance testing?

BDD in Action, Second Edition, Test Driven: Practical TDD and Acceptance TDD for Java Developers, Think Like a Software Engineering Manager, Vibe Engineering and Django in Action.

What should I know before learning acceptance testing?

Manning books that teach acceptance testing usually introduce software testing, unit test, requirements and user story first.

What is the difference between acceptance testing and unit test?

Acceptance testing evaluates whether a system satisfies specified user, business, or stakeholder requirements and acceptance criteria. A unit test is an automated test that checks whether a relatively small unit of software behaves as expected, typically in isolation from external dependencies.

What is acceptance testing a kind of?

Acceptance 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 acceptance testing also called?

Acceptance testing is also called acceptance 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.