I wonder if you guys can help me. I havent had much experience writing test cases. And I need to start now. I need help on the following..
- How do I write test cases without having requirements on hand? Do I just assume the functionality of a feature? How safe is that?
- Do I write a test case for EVERYTHING? Should I cover practically everything on a page with various test cases Or are some meant to be covered exploratorily and through ad-hoc methods. If so, Do I / how do I document them?
Test cases are written only after you know what is the requirement.If there is no written requirement then atleast a prototype of the application may be sufficeint in the intial stages to start writing the test cases.The coverage depends on the functionality ,which gives you an idea of what to test and what not to test.Once you explicitly mention the items not to be tested in the Test Plan,then write test cases for the items which need to be tested which will cover the True and False conditions,and the boundary values.Hope this helps you.
"A ship is safe in the harbor but that is not what ships are meant for."
Well I do have a few Requirements, but they are VERY few and quite vague, and one thing I forgot to mention is that the project is already underway, I joined the team when most of the modules had been 'done'. So I guess that makes it easier to assume a funtionality and write test cases. But I dont suppose thats the best way to go about it, but then again, do I have a choice?
My question about coverage was: How deep into the fuctionality do I go? In the test case, do I mention each and every possibility? I will be testing for it of course, but need all that be in the test case?
well in a test case, it will be a good ethic to write all the possible +ve test cases and the possible -ve test cases and to check on the complete functionality and whatever u test should be in a test case also and that will be the best test ethic to follow.