Acceptance test cases are based on what?

Acceptance test cases are primarily based on requirements. This is because acceptance testing aims to determine whether a system meets the specified requirements and is ready for delivery to the customer or end-users. Acceptance test cases are derived from functional and non-functional requirements, capturing user needs and ensuring that the system behaves as expected under realistic conditions.

These tests often reflect the actual usage scenarios that end-users will encounter, thereby validating that the system not only meets technical specifications but also aligns with user expectations and business objectives. By focusing on requirements, acceptance tests help provide a clear pass/fail criteria that stakeholders can use to decide whether to accept the system for release.

In contrast, while design, code, and decision tables might be part of the overall testing process, they do not form the foundational basis for acceptance test cases. Design focuses on how the system is structured, code relates to the implementation details, and decision tables are tools for managing complex logic rather than sources for acceptance criteria.