Step Sequences

Step Sequences

The simplest way to view a Step Sequence is to think of it as a table or spreadsheet, with the first row or header row always having the same column headings and the first column always being the ID column.

The following table demonstrates the structure of all Step Sequences:

iID	iSeq	cStepType	cField	cValue	cTiming	cExpect	cOnError
Seq001	1	Data
Seq001	2	Step	Login
Seq001	3	Step	BusProcess1
Seq001	4	Step	BusProcess2
Login	1	Text	UserName	MyUserName
Login	2	Text	Password	MyPassword
Login	3	Button		Login		Welcome Users Name	LoginFailedSequence

Explanation of column headings:

Column Name	Value
iID	The ID used to uniquely identify a Step Sequence
iSeq	Optional/Purely cosmetic, only used to help you structure you step sequences
cStepType	The type of Step to execute
cField	Generally used to identify the application field to act on.
cValue	Generally used to contain the data used in acting on a field
cTiming	Generally used as a unique transaction name, in performance tests this would be the name you record the response time of the action against, In a regression test this would be the name you record a pass/fail against for this action.
cExpect	Generally used for storing an expected result to help determine a Pass/Fail for a step, in some cases it could be the same as cValue
cOnError	The step sequence to call if the current step fails, could be used to close and exit the application, for error handling, or to clean up and get back to a known state for the next Step/Test