STOP WRITING THOSE DUMB TEST CASES
Hhhmmm maybe the title is a bit misleading. Or at least it can be.
Are all test cases dumb? It depends on who you ask.
Some may say that not only are test cases by themselves not dumb, they are one of the most versatile and handy tools a tester can use in her work.
Versatile? A test case??? At the end of the day it all comes down to who is writing the test case and what was her intention.
I am tired of the cool context-driven kids implying that writing tests is a waste of testing time. But, I am also tired of those certification-gurus who think that we can describe and classify everything a tester needs to do.
The truth, as it is usually the case, falls somewhere in the middle.
I want to de-vilify the “Test Case” and explain how that actually plays out in the real world, were us testers work as part of teams, where we don’t have enough time to test everything we’d like to test, where we need to help others to test with us, where there is a lot of pressure and a big price if we make mistakes...
We will review how tests can be written to suit the context of the task, how different testers need different tests at different times, and how to research your tests with bigger care so that the written test is smarter and more valuable.
- Don’t surrender to definitions or camps. The correct answer lies in the context of your project and team
- How to make your test cases work by considering the who (is testing), what (is being tested) and when (the time we are given)
- Learn about the different types of test cases you can use depending on the needs and context of your project and team
- How researching and learning around your test case can make it more valuable