I still today meet many people in Denmark in projects and organisations (usually non-tester but also tester) that have very specific ideas about what testing is all about – and yes the words “test cases” do come up in almost every conversation.
I hate the fact that my chosen professional career is regarded as something simple and easy to do and the fact that I have to provide answers for questions like “Why do you need so much time for testing?”, “Is this tool really necessary?”, “Why don’t you just automate the test”, “Why do you need design documentation?”, “How many test cases do you think is needed for this project?”, and so on.
In Testing Trapez issue February 2014 you can find a very important article that I suggest you read if you are a Tester.
TEST CASES ARE NOT TESTING: TOWARDS A CULTURE OF TEST PERFORMANCE (page 30)
By James Bach, Washington, USA and Aaron Hodder, Wellington, New Zealand
Testing is the evaluation of a product by learning about it through experiment; by seeing it in action. The reason we test is to analyse product risk: the danger that the product will cause trouble for its users or otherwise fail in some way to fulfill its purpose. In other words, we look for anything about the product that might significantly impair its value. We are looking primarily for “bugs.” We want to find every important bug, although there will be no way to know for sure that we have succeeded.