Skip to main content

> Term

Acceptance Testing

Formal testing conducted to determine whether or not a system satisfies its business and technical requirements before going to production.

Detailed Explanation

Acceptance testing is the final phase of validation where stakeholders verify if the software meets the agreed-upon criteria. It acts as a gatekeeper between development and production.

Why It Matters

It prevents deploying features that work technically but fail to solve the actual business problem.

Common Failure Mode

Acceptance criteria are vaguely defined, leading to subjective arguments over whether a feature is 'done' while the release is delayed.

Practical Example

A product manager running through a user journey on staging and approving the release.

Production Manifestation

A formal sign-off process, automated end-to-end test suites, or beta environments where product owners interact with the release candidate.

Frequently Asked Questions

What is Acceptance Testing in short?

Formal testing conducted to determine whether or not a system satisfies its business and technical requirements before going to production.

What is the most common failure mode?

Acceptance criteria are vaguely defined, leading to subjective arguments over whether a feature is 'done' while the release is delayed.

AI Summary

Formal testing conducted to determine whether or not a system satisfies its business and technical requirements before going to production. It prevents deploying features that work technically but fail to solve the actual business problem.