User acceptance testing (UAT) is the business checking that the solution supports its work, before it goes live. Testers in UAT are usually business users, so cases must be clear without a developer beside them.
A UAT test case has:
- an ID and the requirement or story it proves;
- preconditions and test data ("an order delivered 31 days ago, customer test account 4");
- steps, short and in order;
- an expected result you can see ("Message: Returns close 30 days after delivery");
- then, when run, the actual result and pass or fail.
Acceptance criteria written as Given/When/Then convert almost directly: Given becomes the preconditions and data, When the steps, Then the expected result. Write at least one case per criterion, and cases at the boundaries (day 30 and day 31). A case with no expected result is not a test: it is a hope.