Commonly, this document starts with a brief description of a GUI event to be tested, we will still use the example about the login attempt. We should specify conditions and steps for executing the test. Finally, we need to evaluate the expected result of the test and define the acceptance criteria for determining whether the test succeeds or fails.

You must keep in mind some considerations such as the ones listed here:

• How often the user interface changes
• How much freedom end users will have when navigating through the application
• If you have testers with less experience, they may need more detailed procedures

What to include? Good question. Similar to our planning template, we need to put our acceptance criteria organized in a document where we can check and save the evolution of each test case. Here's a very basic example:

It's important that you have separated your test data for test cases. Most of the time, issues are products of validation errors in the project, so the development teams must know which parameters caused this error. Always remember that application development is a team work, so you must give all the facilities to your colleagues to get the best product.