Test Scenarios

[thomaskilian]

Hi Testers
probably I've asked this before: can anyone give me a clue on how to model a Test Scenario? That is: I want to line up a number of independant test cases so they build a "story" which will take a tour through the whole system. I could think of using the <<testcase>> Use Cases where a bunch of those hold single test cases and one to <<include>> these, where a number in the relation will show the sequence of usage. Does that make sense?

[sargasso]

Hi thomas,

I've not attempted to do what you are trying because of a difference in philosophy.  I firmly adhere to a "one test for one thing" policy as trying to create a tour approach invariably (IME) results in a script that canot be executed unless all tests pass.

If you are trying to get execution efficiency through the tour approach I'll add one more word of caution.  Where instances of dependency exists between cases if you dont loose on the execution because of the above then you almost certainly will loose in the diagnosis, retest and management areas.

Finally, I reckon that over scripting leads to tunnel vision in the tester - they don't see any problems that you haven't already foreseen.

One test case per scenario - no dependencies between cases - leave enough room for testers to manouver around and find the real problems.

Not an answer, I know.

bruce

[thomaskilian]

Hi Bruce,
I should have been more specific about my background. Testing is only one aspect I want to cover. The other is, that for demonstration purpose (strictly: a certification procedure) I'd like to write down all steps. Since all steps taken can also be looked at as single test scenarios, I'd like to have a tool to bring these in a certain order. Obviously this is nothing used by many people. I'll have to experiment then