Within a , each case generates a large amount of data, which is used as input to the next case in the sequence. Frequently we want to manipulate the data to cause failures in or otherwise the downstream tools. These manipulations are significant whose outputs can be reused in other suites, so I’d like to track them separately from the .

Since the test activities themselves have similar fields to the test cases (precondition, postcondition, etc.) my naive inclination is to capture them alongside test cases (TC), with a different identifier (TA), in the same spreadsheet:

Gumdrop test case spreadsheet

(Additional fields, not shown, are Traceability, Input, Steps, Actual Output, Test Result, and Status.)

Further extending my naive inclinations, I could add preparation/automation activities and track these separately. For all intents and purposes, we can assume this is captured in an Excel spreadsheet or similar and that we can add any fields we need.

Gumdrop test case spreadsheet with additional test activities, duration and resource

This seems fairly nonstandard, so I appreciate any thoughts/alternatives.

Source link https://sqa.stackexchange.com/questions/35576/how-to--test-activities-that-take--between-test-cases-in-a-test-sui


Please enter your comment!
Please enter your name here