This interface is implemented by PageElement, PageElementList, PageElementMap and PageElementGroup.
IElementNode guarantees support of the following state retrieval functions:
IElementNode guarantees support of the following state check functions:
Extracts the return value types of the getIsEnabled functions of all PageNodes defined within a PageElementGroup's
content. For a PageElement, the extract return value type will be boolean.
Extracts the return value types of the getIsEnabled functions of all PageNodes defined within a
PageElementGroup's content for state check functions. For a PageElement, the extracted return value
type will be boolean.
Compared to ExtractBoolean, this will allow the a PageElementList to pass either a single boolean or
an array of booleans.
Extracts the return value types of the getText functions of all PageNodes defined within a PageElementGroup's
content. For a PageElement, the extract return value type will be string.
Extracts the return value types of the getText functions of all PageNodes defined within a PageElementGroup's
content for state check functions. For a PageElement, the extracted return value type will be string.
Compared to ExtractText, this will allow a PageElementList to pass either a single string or
an array of strings.
Extracts the return value types of the getValue functions of all PageNodes defined within a
ValuePageElementGroup's content.
Extracts the return value types of the getHasValue functions of all PageNodes defined within a
ValuePageElementGroup's content. For a ValuePageElement, the return value type will be boolean.
Extracts the return value types of the getValue functions of all PageNodes defined within a
ValuePageElementGroup's content for state check functions and the setValue function.
Compared to ExtractValue, this will allow ta PageElementList to pass either a single value or
an array of values.
IOptStepParams are supposed to be used as the parameters of a step creation function if a step does not require any or only optional arguments.
Steps consist of a description and an execution function. The execution function performs changes to the state of the tested application and the description briefly summarizes these changes in natural language.
A step can be parameterized by passing step arguments and a step callback (both of which are optional) to the execution function:
Step arguments are key-value pair objects that provide dynamic values to the state changes of the execution function.
They also enable the interpolation of a step's description by replacing %{key} in the description string
with key's value retrieved from the step arguments object).
Step callbacks can be used to query and validate the state of the tested application right after step execution. A step callback will be passed the return value of the execution function as its first parameter.
IStepParams are supposed to be used as the parameters of a step creation function if a step requires mandatory step arguments.
Severity describes how severe the implications of something not working correctly would be.
The result status of a validation/an acceptance criteria of a Story.
Steps in wdio-workflo need to be defined in this format - on object where the keys are the step descriptions and the values are step creation functions that take the step parameters as and argument and return a created Step.
The result status of a testcase.
This interface is implemented by ValuePageElement, ValuePageElementList, ValuePageElementMap and ValuePageElementGroup.
IValueElementNode guarantees support of the following state retrieval functions:
IValueElementNode guarantees support of the following state check functions:
The default interval value used in functions that operate with intervals if no other interval is specified in workflo.conf.ts, in the PageNode itself or as a parameter passed to the function.
The default timeout value used in functions that operate with timeouts if no other timeout is specified in workflo.conf.ts, in the PageNode itself or as a parameter passed to the function.
Mixes baseCtors classes into derivedCtor class. All properties of baseCtors will be written to derivedCtor. If a property with the same name already exists in derivedCtor, it will be overwritten. For more information about typescript mixins see https://www.typescriptlang.org/docs/handbook/mixins.html
the class into which baseCtors should be mixed in
the classes which should be mixed into derivedCtor
If the name of property is contained in mergeObjectKeys and the property exists as an object in both derivedCtor and baseCtor, both objects will be merged together instead of the baseCtor object overwriting the derivedCtor object. Be aware that deep merging is not supported and therefore "nested" properties with the same name in derivedCtor's object and baseCtor's object will still be overwritten by baseCtor's object values.
Use this function to create step definitions and preserve their types.
An object whose keys are step descriptions and whose values are step creation functions.
Returns true if:
an arbitrary value
Returns true if the passed node supports all functions defined in IElementNode.
a PageNode
Returns true if the passed node supports all functions defined in IValueElementNode.
a PageNode
Returns true if the passed result is an instance of Workflo.IJSError.
an arbitrary value/object
Returns true if value is null or undefined.
an arbitrary value
Returns true if value is neither null nor undefined.
an arbitrary value
Creates a Proxy that adds custom getters and setters to the merged step definitions. Steps in wdio-workflo can only function properly if this proxy is used to interact with them.
the merged step definitions
the proxified steps
Prints values with tolerances as a string.
a number or an object with values of type number
a number or an object with values of type number
Generated using TypeDoc
A function used to clone a PageElementList.
Type the type of the cloned list
the selector of the cloned list