🖐🏾 👃🏽 🚣🏾 Experienced tester's crystal ball 🔟 🔎 🚬

This blog is all about thinking about the past, present, and future in testing. As much as I want to see everything clearly, my crystal ball is rather dim. However, learning is necessary, and here is my tool for that.

Difference between test idea and test case?

Year after year, changing organization one after another, I come to a new venture with the anticipation that I will not have to see test cases other than those that are automated, and through continuous execution keep constant updating.

And yet, year after year, as I move from one organization to another, I learn that people are still writing test cases. These are the test cases that contain the title and the steps to be taken. Those that define the sequence of actions in the application that need to be checked and the steps that you may or may not follow because you are not a robot.

From my point of view, ideas are of no value, and we care little how well they are documented. Ideas written on pieces of paper are often difficult for me to decipher after a month, but these are critical notes and I really need them when I return to the pre-structured information that I previously documented. Test cases are what we might want to leave for later, they are more than ideas. They have a structure that keeps them running, even if they look like a checklist. They often include steps and ideas for ordering. It is better to consider test cases as the result of testing (moreover, automated!), And not as initial data for testing.

, , , . , , , , , .

/ , , , — , , . . , , 1, — 2 . , .

20 , , . , — . , , , , , , .

, .