Mocker Commands

Mocker commands connect QaaS.Runner tests to QaaS.Mocker servers. They let a test change mock behavior, trigger mock-side actions, or consume mock activity.

For the transport-side configuration, see QaaS.Mocker Servers.

Some mocker commands do not produce session data. Others interact with the mocker's data and create Input and Output values in SessionData depending on the command type.

Table Property Path - Sessions[].MockerCommands[]

ChangeActionStub

Changes the stub for a specific mock action endpoint.

Table Property Path - Sessions[].MockerCommands[].Command.ChangeActionStub

Type: ChangeActionStub
ChangeActionStub: {}

TriggerAction

Triggers a mock action endpoint.

Table Property Path - Sessions[].MockerCommands[].Command.TriggerAction

Type: TriggerAction
TriggerAction: {}

Consume

Consumes data received by the mocker and data sent by the mocker.

Table Property Path - Sessions[].MockerCommands[].Command.Consume

Consume: {}

Data Structure

Input

Body: <byte[]>
MetaData:
    Http:
        Uri: <Uri>
        RequestHeaders: <IDictionary<string, string>>

Output

Body: <byte[]>