KeywordBlock Element/en
A keyword driven test is defined by a sequence of test steps, each of which consists of a keyword (the test action, such as "click" or "input"), a number of optional input parameters ("what to input"), possible validations ("what should be shown") and possibly forwarding information for any values ("remember field contents in $foo"). In being a subset of the full activity diagram (with a different presentation), such a sequence can of course also be represented as a sequential list of steps (only connected by enable-output/enable-input connections).
The keyword driven test action description can be used to define simple sequential test or test step sequences. The sequence is defined in tabular format, which some users prefer over full blown activity diagrams.
Rules[Bearbeiten]
All actions within the test suite can be used as "keyword" actions if they match the following rules:
- They either have no input/output pins or only input/output pins with one of the following data types: String, Number or Boolean.
Keyword driven test action descriptions can be mixed up in a compound action description with all other action descriptions without any limitation.
Execution and Logging[Bearbeiten]
During execution each action is executed one after the other. Please be careful using blocks producing more than one data at the output. In that case the data stored in a connected variable is the last value written to the output pin. Also the defined assertion will be executed only for the last written value.
The log and report format is equal to compound blocks.
Converting[Bearbeiten]
Keyword driven test action descriptions can be converted to compound action descriptions. Compound action descriptions can be converted to keyword driven test actions only if they have no parallel steps, loops or branches. Connections between steps are converted to environment variables as data holders.
