Summary
We are now fully familiar with test cases and their alternatives. We learned how to write great test cases, examined some examples of what they look like, and learned more about when it’s not ideal to use them. Furthermore, we also covered their alternatives, their advantages, and when they are appropriate for use. The desired outcome of a test case is a bug and in the next chapter, we will start our journey into bugs in great detail. We will build on what we have learned about test cases and see how bug reporting works, how it flows between the game team, and how QA fits into this process.