What must the acceptance criteria for a use case at a minimum include?

The acceptance criteria for a use case should, at a minimum, specify one test case for the main path and one test case for each alternate path. This ensures comprehensive testing of the use case's functionality, addressing both the most common scenario (the main path) and any variations (the alternate paths).

By including a test case for the main path, you verify that the core functionality works as expected. Additionally, incorporating test cases for each alternate path ensures that all possible scenarios are considered and validated. This is crucial in ensuring that the system behaves correctly under various conditions, which reflects real-world usage where users may interact with the system in different ways based on their needs or situations.

Overall, this approach fosters a robust understanding of the use case's reliability and performance, as it encapsulates the full range of expected outcomes and exceptions. Without adequate coverage of both the main and alternate paths, there is a risk of incomplete testing, which could lead to undetected bugs or user dissatisfaction.