What are Use Cases/Test Cases and how should they be answered?

Even though the terms are often used similarly, use cases and test cases are very different (see table below). Both terms refer to forms of “tasks” that you have to do during testing. We use them to make sure you cover everything the client wants to have tested.
 Use Cases                                             “Open” task: Something that a regular user might want to do.  Made up of several sub-tasks (e.g. clicks, actions) that the users have to find by themselves and do one after the other. They are not spelled out in the use case.  Has to be answered in form of a text, listing step by step how you proceeded.Example Use Case: “Find a pair of brown shoes on the website”.This task could be completed by typing “brown shoes” in the search OR clicking the category  “shoes” and looking for brown ones OR using a filter function (each made up of different sub-tasks).Test Cases  Specific task: one exact action.   A very simple task that is clearly stated.There is only one way of doing the test case.  If the task is successful, you just have to choose “OK”. Otherwise choose “Not OK” and you may be asked to submit a Bug report.Example Test Case: “Click on the ‘Shoes’ button”.There is usually no room for interpretation: one button and one way of clicking (clicks are by default left-clicks). About Use CasesWe know, it can sometimes feel a bit boring to write down all the steps you took, especially if they seem obvious. But they are not always that obvious to others; and how you write your answers is exciting to read for Testbirds and its clients! It is interesting to see how you approach the task and sometimes this can already be useful feedback in itself, because the client might think that people use the product differently.Please remember to:
List ALL your actions, step-by-step in a bullet point list.Don't include any feedback in your answer to the use case. There are usually other sections of the test report asking about what you liked/disliked.Write down WHERE you clicked - ensure that you include any: tab headers, page names, hyperlink labels, article titles, button names or image/textbox labels etc.Describe your actions: e.g. clicked on, scrolled to, hovered over, selected, tapped, opened, typed etc.Example Use Case (“Task”): Find out what is on the menu at a Ben and Jerry's Scoop Shop.(A good answer would be something like:)

1. I hovered over Scoop Shops on the top navigation bar. A sub-menu opened.
2. Clicked on Your Local Scoop Shop
3. Scrolled down to where it says Scoop Shop Menu and found 3 menus listed there: Sundaes, Shakes, and Flavours
4. Clicked on "Flavours" to see what ice cream flavours they sell at their shops
5. Selected Peanut Butter Cup and read the ingredients and nutrition facts