Tester, might it simplify things to have AUT scenarios based upon Use Cases? Ideally, Use Cases are representative of the ways in which end-users actually use the system. Thus the AUT amounts to a demonstration as is the case with many organizations. At the point of AUT one should assume that upstream testing has identified most defects, and that those were repaired, or - are documented with workarounds to get through AUT. And ideally, there should be plans to fix the outstanding known defects.
yup alex you are right........basically when it comes down to testing it is same across companies only the processes we follow may differ.
When you test scenarios also called Use Cases, it is the flow of the application when a particular action is done. A scenario would include both positive as well as negative cases.
e.g. visualize the Login Process it has to include what happens when the user enters valid UID and PWD and the vice versa also
Thanks a lot for confirmations that my guess is right! [img]/images/graemlins/smile.gif[/img]
Rich: You're totally right with your additional tests to be covered.
My example scenario here was a bit too broad I guess...
In the tests i'm currently executing, the "PO modification" in itself is a scenario and e.g. PO cancellation or invalid PO data is a test case within that scenario. Wrong approach?
Otherwise I'd end up splitting the case off in different steps again. Would that also be a good approach?
Scenario -> Case -> Step? I personally think that'd get one lost in too many "subsections"...