How low do you go?
Or perhaps it's high. I can never remember. In any case, I ran into an odd problem today, although I am thoroughly ecstatic to be running into this.
In the last 5 years that I have been doing QA, I have never been given a requirements document. I started with a new company a few months ago which seemed to be the same ol' "You have 8 hours for testing, ask the dev what it's supposed to do and make sure it does it." I tell you, I am pro at figuring out what requirements were without ever being told. But today, today that all changed. I was handed a specifications document of all things! Honestly, I nearly cried I was so happy.
Now for my problem: since I've never actually written test cases from a document before, how specific do you normally get? Do I write items such as "Verify that record 2 can be entered, and that it can be modified during and after saving." for every item in the spec doc? Or do you usually list "Test the functionality of record 2"? I'm stumped between the two. On the one hand, we have a very detailed Sprint cycle, with smaller burn cycles detailed out, so I could write a suite for each burn cycle, and compose those into a suite for the sprint, and use those (once updated during the burn/sprint) as regression tests for the later sprints or I could let the burn cycle speak for itself - "Developer Infrastructure" turns into "Test Infrastructure" though that seems a bit too lackadaisical for my planning streak.
Or maybe, I'm just so excited about this I've lost the entire string of thoughts in a jumble of "It's a real, live SPEC DOC! I only dreamed they could exist!"
Thanks in advance for any comments you may have. Unless it's teasing me about my happiness over a piece of paper (or 65). I'm holding on tightly to this little piece of heaven and I'm not letting you bring me down! :P
Re: How low do you go?
Congratulations on that significant milestone, or - kilometerstone if you are on the metric system.
Test case detail level? It depends upon many things...
1. Level of detail required per your "faithfully reproduce" criteria.
2. Will others execute these?
3. Will novices execute these?
4. If a contract is involved, what does the contract require?
- Here is an example of detail. It more geared toward addressing a question of manual data-driven testing. I would consider the level less than faithfully reproducible.
Re: How low do you go?
Thanks Jake! I should have known to think about that before I write anything, but the excitement got the best of me. Thanks for the reminder!
It will only be me, as I'm the sole QA, sole tester, and lone ranger on the front. These will, however, possibly be used as reference for unit tests. I don't think the devs have quite figured out how they're doing the testing yet (yay for develop now, test later thinking. . . Gives me more to do?) and will probably be doing it last minute when I refuse to accept a build without some sort of testing on it.
I think I've decided I'll get as specific as I can with this document (which is pretty darn good *glee*) and then update as I receive things. It should keep it pretty structured as this will also be the first time a team has decided to do a true Sprint model, rather than making plans and scrapping them because they can't meet goals. This project is just wowing me all over the place. Hurray for company-wide New Year's Resolutions!