Today, I would like to talk about Test Cases. I remember the first time I had to write a test case, I only had some basic requirements about a system, no idea how it worked, and a distant idea on how I would start my first test case.
Logically the first step was to read old test cases that have been written by others Test Analysts. So I verified the requirement specification and checked the related test cases. The first thing I learned was that each Tester have a particular way of writing their own test cases. In addition, some test cases are simpler than others (one might say they are just clearer). Following this line of thought, I decided to use the simplest test cases I could put my hands on, and use them as templates for my test cases. This proved to be really rewarding, as it allowed me to make easier and clearer test cases.
There are different ways to write test cases. I will try to exemplify some of them:
This is the usually the method which is used the most. The issue is that sometimes we do not have much time to add details the test case, and when the requirements are updated, this kind of mode ends up taking even more time and effort. What usually happens is that the test case becomes inconsistent with the system, or they get incomplete very fast (that is, do not test all the requirements of the system).
Wherefore, I suggest another approach for writing test cases. I think it is more effective to validate the possible values for each field, and the total of combinations for it, making it clearer and easier to update the test cases.
Below, I also added other models that I think could be useful. I got these examples from some QA friends, which allowed me to share their materials.