MockMotor

GraphQL

Path in Request

If the request is in GraphQL format, this field specifies where to look for GraphQL query or mutation.

If the whole request payload is GraphQL, as in

{ hero { name class }}

use

input

If GraphQL is in a JSON property of the request payload, as in

{
  "query":"{ hero { name class }}"
}

use path to property

input.query

If GraphQL is in an HTTP parameter, as in

/npc?q={%20hero%20{%20name%20class%20}}

use path from HTTP

http.parameters.q

See the variables cheatsheet for more info.

Match Options

HTTP Method

Relative URI

SOAP Action

First Element of XML Payload

Script

The part of the URI left after the service URL is removed.

The URI can contain parameters, like in

/user/{userId}/statement/{statementId}

The parameters are placed into the variables with matching names (userId and statementId in this case). They are also placed into the rest variable structure.

The special catch-all variable format is

/acc/{alltherest:.*}

Here the variable alltherest catches all URI data after acc.

See the variables cheatsheet for more info.

For SOAP payloads, this is the name of the first element under soap-env:Body, without the namespace.

For example, in

<soap-env:Envelope><soap-env:Body><user:GetCurrentUser>...</soap-env:Body></soap-env:Envelope>

the first element is GetCurrentUser.

For non-SOAP payloads, this is the name of the first element of the payload, without the namespace.

For example, in

<id:GenerateID><id2:Format>UUID</id2:Format></id2:GenerateID>

the first element is GenerateID.

The script can use any of the inbound variables.

For Javascript expressions, the boolean true value or any non-null value means a match.

For XQuery expressions, the boolean true value or any non-empty sequence value means a match.

Examples:

What to check	JS	XQ
Property exists in the payload	input.user.birthDate	$input//*:birthDate
Property in the payload matches a value	input.user.id=='120000'	$input//*:id='120000'
Header matches a value	http.headers['X-TxId']=='8'	$input//*:header[@name='X-TxId']/text()='8'
Account property matches a value. Note: the account must be selected in the Accounts section.	account.level=='BASIC'	$account//*:level/text()='BASIC'
HTTP parameter	http.parameters.id=='0'	$http//*:parameter[@name='id']/text()='0'
HTTP method	rest.method=='GET' \|\| rest.method=='XGET'	$rest//*:method/text()=('GET','XGET')
Random value (for intermittent responses)	mockmeta.random < 0.1	$mockmeta/random < 0.1

Use logical OR or AND when necessary

Examples:

Expression	JS	XQ
Either of accounts	input.account=='100500' \|\| input.account=='100522'	$input//:account='100500' or $input//:account='100522'
Checking two properties	input.ban=='123' && input.mdn=='4168221108'	$input//:ban='123' and $input//:mdn='4168221108'

See the variables cheatsheet for more info.

Test-execute the script using the Run button on the right side of the field.

Account(s) Selection

Select mock accounts where properties are matching request values

If None Found

Fail Immediately Ignore & Continue Create New

Max Accounts

Forward to Live Service

Forward URL

Append Relative URI

Append Skip

Append Query Parameters

Append Skip

Read timeout, ms

Payload for Forward

Cache Transactions

Cache Don't

Cache Keys

Specify the key values that differ one transaction from another, one per line. Usually those are the account numbers, but can also be addresses, currencies etc.

For each unique combination of keys' values, a new cached reaction is created. The reaction uses a script to match any request that contains the same key values, as well as the same HTTP method, relative URI and SOAPAction/top XML element (for XML requests).

For instance, the key can be

input.account.id

. The matching script in the cached reaction then can be

input.account.id=='18474332674'

And, for another request, another cached reaction can be created, with

input.account.id=='22274332811'

For complex cases, you can provide a complex multiline script that computes the key, for example

concat($input//*:id,substring($input/tx,1,3))

The cached reactions are marked as such in the reactions list. They can be deleted in bulk from the service and environment pages.

Response Payload

Payload Prettify De-Prettify

... or upload it

Upload

For static XML response, place XML as-is:

<Data>
	<Error Code="0011"/>
</Data>

Note: for SOAP responses, add Envelope, Header and Body. MockMotor doesn't do that automagically.

For computed XML response, use XQuery:

<Data>
{
	for $code in $input//*:code
	return
		<Warning Message="Not Found" Code="{$code}"/>
}
</Data>

For static JSON, YAML or text responses, use the response payload as-is:

{
  "profile": {
	"id": 100500,
	"firstName": "John"
  },
  "status": "success"
}

For computed JSON responses, use Javascript and assign the result to the output variable:

var fibo = [];
fibo.push(1);
fibo.push(1);

for(var i=1; i<10; i++) {
	var len = fibo.length;
	var next = fibo[len-2] + fibo[len-1];
	fibo.push(next);
}

output = 
{
  "fibo": fibo,
  "status": "success",
  "ref": jsonPath("$..transactionId")
}

If forward to a live backend is used, you can leave this field empty to return the response that the backend provided. That response is saved into the output variable, so you can alter it before sending it back to the application.

See the variables cheatsheet for more info.

Test-execute the script using the Run button on the right side of the field.

Response Properties

HTTP Status

Content-Type

Delay, ms

Response HTTP Headers

Response Attachments

Attachments

Style

MIME/SWA MTOM/XOP

Specify the attachment names and optionally properties.

Adding one attachment by name:

Contract.pdf

Adding a group of attachments by name, their IDs and Content-Types are read from the mock environment:

["Contract.pdf","Addendum.pdf"]

Adding a group of attachments by name, with specific IDs and Content-Types:

[{"name":"Contract.pdf","content-id":"100","content-type":"application/pdf"},{"name":"Addendum.pdf","content-id":"200","content-type":"application/pdf"}]

Update/Delete Mock Account(s)

Update Account(s)

Same Values for All Accounts Distinct Values for Each Account

Delete Account(s) If

The script is exacuted with every selected account. If the result is true, the account is deleted.

To delete all selected accounts, put 'true' or 'all' into this field:

true

To delete some of the selected accounts, use a script that returns true for accounts that must be deleted:

JS:

// remember that account values are strings. Use parse* functions to compare to numbers.
output = account.status == "DONE" || parseInt(account.priority) < 10;

XQ:

$account/status="DONE"

Postponed Background Request

Postpone, ms

Method

URL

Content-Type

Headers

Payload

Search Results for [] in

Mock_Environments

Execution

After Execution

Advanced

Advanced