Templating¶
Hoverfly can build responses dynamically through templating. This is particularly useful when combined with loose matching, as it allows a single matcher to represent an unlimited combination of responses.
Enabling Templating¶
By default templating is disabled. In order to enable it, set the templated
field to true in the response of a simulation.
Getting data from the request¶
Currently, you can get the following data from request to the response via templating:
Field |
Example |
Request |
Result |
---|---|---|---|
Request scheme |
|
http |
|
Query parameter value |
|
bar |
|
Query parameter value (list) |
|
bar2 |
|
Path parameter value |
|
one |
|
Method |
|
GET |
|
Host |
|
www.foo.com |
|
jsonpath on body |
|
{ “id”: 123, “username”: “hoverfly” } |
123 |
xpath on body |
|
<root><id>123</id></root> |
123 |
From data |
|
||
Header value |
|
{ “X-Header-Id”: [“bar”] } |
bar |
Header value (list) |
|
{ “X-Header-Id”: [“bar1”, “bar2”] } |
bar2 |
State |
|
State Store = {“basket”:”eggs”} |
eggs |
Helper Methods¶
Additional data can come from helper methods. These are the ones Hoverfly currently support:
Description |
Example |
Result |
---|---|---|
The current date time with offset, in the given format. For example:
|
|
|
A random string |
|
hGfclKjnmwcCds |
A random string with a specified length |
|
KC |
A random boolean |
|
true |
A random integer |
|
42 |
A random integer within a range |
|
7 |
A random float |
|
42 |
A random float within a range |
|
7.4563213423 |
A random email address |
|
|
A random IPv4 address |
|
224.36.27.8 |
A random IPv6 address |
|
41d7:daa0:6e97:6fce:411e:681:f86f:e557 |
A random UUID |
|
7b791f3d-d7f4-4635-8ea1-99568d821562 |
Generate random data using go-fakeit |
|
John Smith |
Query CSV data source where ID = 3 and return its name |
|
John Smith |
|
|
John Smith |
Time offset¶
When using template helper method now
, time offset must be formatted using the following syntax.
Shorthand |
Type |
---|---|
ns |
Nanosecond |
us/µs |
Microsecond |
ms |
Millisecond |
s |
Second |
m |
Minute |
h |
Hour |
d |
Day |
y |
Year |
Prefix an offset with -
to subtract the duration from the current date time.
Example time offset¶
5m |
5 minutes |
1h30m |
1 hour 5 minutes |
1y10d |
1 year 10 days |
Date time formats¶
When using template helper method now
, date time formats must follow the Golang syntax.
More can be found out here https://golang.org/pkg/time/#Parse
Example date time formats¶
2006-01-02T15:04:05Z07:00 |
Mon, 02 Jan 2006 15:04:05 MST |
Jan _2 15:04:05 |
Note
If you leave the format string empty, the default format to be used is ISO 8601 (2006-01-02T15:04:05Z07:00).
You can also get an UNIX timestamp by setting the format to:
unix
: UNIX timestamp in secondsepoch
: UNIX timestamp in milliseconds
Faker¶
Support for go-fakeit was added in order to extend the
templating capabilities of Hoverfly. Faker covers many different test data requirements and it can be used within
Hoverfly templated responses by using the faker
helper followed by the faker type (e.g. Name
, Email
)
For example, you can generate a random name using the following expression:
{
"body": "{\"name\": \"{{faker 'Name'}}\"}"
}
Fakers that require arguments are currently not supported.
CSV Data Source¶
You can both query data from a CSV data source as well as manipulate data within a data source by adding to it and deleting from it. Hoverfly supports a number of templating methods for simple read, update and delete functions. In addition Hoverfly supports a templating function that allows simple SQL like commands for SELECT, UPDATE and DELETE.
Reading from a CSV Data Source¶
You can read data from a CSV data source in a number of ways.
The most basic is to use the csv
function to return the value of one field (selected-column) given a field name to search (column-name) and
a value to search for in that field (query-value). Of course the query-value would normally be pulled from the request.
Note
The data source name is case sensitive whereas other parameters in this function are case insensitive. You can use hoverctl or call the Admin API to upload CSV data source to a running Hoverfly instance.
Example: Start Hoverfly with a CSV data source (student-marks.csv) provided below.
hoverfly -templating-data-source "student-marks <path to below CSV file>"
ID |
Name | Marks |
1 |
Test1 | 55 |
2 |
Test2 | 65 |
3 |
Test3 | 98 |
4 |
Test4 | 23 |
5 |
Test5 | 15 |
NA | 0 |
Description |
Example |
Result |
---|---|---|
Search where ID = 3 and return name |
csv ‘student-marks’ ‘Id’ ‘3’ ‘Name’ |
Test3 |
Search where ID = 4 and return its marks |
csv ‘student-marks’ ‘Id’ ‘4’ ‘Marks’ |
Test23 |
Search where Name = Test1 and return marks |
csv ‘student-marks’ ‘Name’ ‘Test1’ ‘Marks’ |
55 |
Search where Id is not match and return marks (in this scenario, it matches wildcard * and returns) |
csv ‘student-marks’ ‘Id’ ‘Test100’ ‘Marks’ |
0 |
Search where Id = first path param and return marks URL looks like - http://test.com/students/5/marks |
csv ‘student-marks’ ‘Id’ ‘Request.Path.[1]’ ‘Marks’ |
15 |
Additional functions are avaiable to query the CSV data source to return all or a filtered subset of it’s rows, as a map.
This makes it simpler to render back into the template, as you can use the {{this}} expression with the column names to identify which fields you want to render.
To return all the data from the csv as an array of maps, you use the csvAsMap
function.
(Note that you would need to wrap this in an #each block. See examples below.):
To return filtered data from the csv as an array of maps, you use the ``csvMatchingRows``function. (Note that you would need to wrap this in an #each block. See examples below.):
To return all the data from the csv as an array arrays, you use the csvAsArray
function.
(Note that you would need to wrap this in an #each block. See examples below.):
To return filtered data from the csv as an array of maps using the SQL like dialect, you use the csvSqlCommand
function.
Again this needs to be wrapped in an #each block:
Example: Start Hoverfly with a CSV data source (pets.csv) provided below.
hoverfly -templating-data-source "pets <path to below CSV file>"
ID |
Category |
Name |
Status |
1000 |
birds |
Archie |
available |
1001 |
dogs |
Zipper |
available |
1002 |
dogs |
Teddy |
sold |
Description |
Example |
Result |
Return all the results in an array of maps and render them in JSON *Note the use of
|
} |
} |
Return filtered data as an array of maps and render them in JSON *Note the use of
|
} |
} |
SELECT data using a SQL like syntax. |
{{#each (csvSqlCommand “SELECT * FROM pets WHERE category = ‘dogs’ AND id >= ‘2000’”)}}
} |
} |
Return all the data as an array of arrays |
{{#each (csvAsArray ‘pets’)}} {{#each this}}{{this}} {{/each}} |
id category name status 1000 cats Sylvester available 1001 dogs Zipper available 1002 dogs Teddy sold |
Adding data to a CSV Data Source¶
While the service is running you can add new rows of data into the data source. This is not peristent, it is only manipulated in memory and so it only lasts for as long as the service is running and between calls. The rows are not actually written to the file.
You use the csvAddRow
function to add a row to the data source.
This is currently the only way to add rows to the datasource. There is no support for SQL INSERT statements.
To use this function you first need to construct an array containing the row of string values to store in the csv data source. For example say you had a csv called pets with the columns id, category, name and status.
You would first add each of the 4 values into an array of 4 items to match the number of columns:
{{ addToArray 'newPet' '2000' false }}
{{ addToArray 'newPet' 'dogs' false }}
{{ addToArray 'newPet' 'Violet' false }}
{{ addToArray 'newPet' 'sold' false }}
You then call the
csvAddRow
function to add the row into the csv data store:
{{csvAddRow 'pets' (getArray 'newPet') }}
Deleting data from a CSV Data Source¶
While the service is running you can delete rows of data from the data source. This is not peristent, it is only manipulated in memory and so it only lasts for as long as the service is running and between calls. The rows are not actually deleted from the file.
There are two ways to delete rows. This first simple method using csvDeleteRows
will delete rows that match one exact condition.
To delete rows from the csv data source your specify the value that a specific column must have to be deleted.
To delete all the pets where the category is cats from the pets csv data store:
{{ csvDeleteRows 'pets' 'category' 'cats' false }}
Note that the last parameter of “output-result” is a boolean. It is not enclosed in quotes. The function will return the number of rows
affected which can either be suppressed by passing false to this parameter, or passed into another function if you need to make logical
decisions based on the number of rows affected by passing in true as the last parameter. If csvDeleteRows
is not enclosed within another
function it will output the number of rows deleted to the template.
- ``{{#equal (csvDeleteRows ‘pets’ ‘category’ ‘cats’ true) ‘0’}}
{{ setStatusCode ‘404’ }} {“Message”:”Error no cats found”}
- {{else}}
{{ setStatusCode ‘200’ }} {“Message”:”All cats deleted”}
{{/equal}}``
Deleting data from a CSV Data Source using SQL like syntax¶
Example:
{{ csvSqlCommand "DELETE FROM pets WHERE id > '20'" }}
Calling the csvSqlCommand for Delete and Update commands will execute the statements without outputting anything to the template. The rows affected will be logged for debugging purposes.
Update the data in a CSV Data Source using SQL like syntax¶
Example:
{{ csvSqlCommand "UPDATE pets SET status = 'sold' WHERE id > '20' AND category = 'cats'" }}
Using SQL like syntax to query and manipulate data sources¶
You can use a simplified SQL like syntax to select, update and delete rows.
INSERT is not supported. To add data you must use the csvAddRow template function.
SELECT [column-names] FROM [data-source-name] WHERE [conditions] (* can be used to indicate all colmuns)
UPDATE [data-source-name] SET [[column-name] = ‘[value]’,] WHERE [conditions]
DELETE FROM [data-source-name] WHERE [conditions]
Only simple conditions are supported.
You can chain conditions using AND. OR is not supported.
The following comparison operators are supported in conditions: = equals > greater than < less than >= greater than or equal to <= less than or equal to != not equal to
Capitalisation of SQL keywords is required. Spaces between components of the SQL statement are required. Every value provided to a condition whether a number or a string must be enclosed in quotes. Joins across different data sources are not supported.
Counting the rows in a CSV Data Source¶
You can return the number of rows in a csv dataset using csvCountRows
.
This will be 1 less than the number of rows as the first row contains the column names.
Journal Entry Data¶
Journal Entry can be queried using its index and its extracted value.
Syntax
{{ journal "index name" "extracted value" "request/response" "xpath/jsonpath" "lookup query" }}
index name
should be the same key expression you have specified when you enable the journal index.
extracted value
is for doing a key lookup for the journal entry from that index.
request/response
specifies if you want to get data from the request or response.
xpath/jsonpath
specifies whether you want to extract it using xpath or json path expression.
lookup query
is either jsonpath or xpath expressions to parse the request/response data.
Example:
{
"body": "{\"name\": \"{{ journal 'Request.QueryParam.id' '1' 'response' 'jsonpath' '$.name' }}\"}"
}
In the above example, we are querying the name from JSON response in the journal entry where index Request.QueryParam.id
has a key value of 1.
If you only need to check if a journal contains a particular key, you can do so using the following function:
{{ hasJournalKey "index name" "key name" }}
Key Value Data Store¶
Sometimes you may need to store a temporary variable and retrieve it later in other part of the templated response. In this case, you can use the internal key value data store. The following helper methods are available:
Description |
Example |
Result |
---|---|---|
Put an entry |
|
123 |
Get an entry |
|
123 |
Add a value to an arra |
|
John |
Get an array |
|
[]string{“John” |
addToArray
will create a new array if one doesn’t exist. The boolean argument in putValue
and addToArray
is used to control whether the set value is returned.
Note
Each templating session has its own key value store, which means all the data you set will be cleared after the current response is rendered.
Maths Operations¶
The basic maths operations are currently supported: add, subtract, multiply and divide. These functions
take three parameters: two values it operates on and the precision. The precision is given in a string
format such as '0.00'
. For example {{ add 3 2.5 '0.00' }}
should give you 5.50
.
If no format is given, the exact value will be printed with up to 6 decimal places.
Description |
Example |
Result |
---|---|---|
Add |
|
13.33 |
Subtract |
|
7 |
Multiply |
|
30 |
Divide |
|
3.333333 |
A math functions for summing an array of numbers is also supported; it’s usually used in conjunction
with the #each
block helper. For example:
With the request payload of
{
"lineitems": {
"lineitem": [
{
"upc": "1001",
"quantity": "1",
"price": "3.50"
},
{
"upc": "1002",
"quantity": "2",
"price": "4.50"
}
]
}
}
We can get the total price of all the line items using this templating function:
{{#each (Request.Body 'jsonpath' '$.lineitems.lineitem') }}
{{ addToArray 'subtotal' (multiply (this.price) (this.quantity) '') false }} {{/each}}
total: {{ sum (getArray 'subtotal') '0.00' }}
String Operations¶
You can use the following helper methods to join, split or replace string values.
Description |
Example |
Result |
---|---|---|
String concatenate |
|
beehive |
String splitting |
|
[]string{“bee”, “hive”} |
Replace all occurrences of the old value with the new value in the target string |
(where Request.Body has the value of
|
to mock or not to mock |
Return a substring of a string |
|
long |
Return the length of a string |
|
21 |
Return the rightmost characters of a string |
|
ing |
Validation Operations¶
You can use the following helper methods to validate various types, compare value, and perform regular expression matching on strings.
Description |
Example |
Result |
---|---|---|
Is the value numeric |
|
true |
Is the value alphanumeric |
|
false |
Is the value a boolean |
|
true |
Is one value greater than another |
|
false |
Is one value less than another |
|
true |
Is a value between two values |
|
false |
Does a string match a regular expression |
|
true |
Conditional Templating, Looping and More¶
Hoverfly uses the https://github.com/aymerick/raymond library for templating, which is based on http://handlebarsjs.com/
To learn about more advanced templating functionality, such as looping and conditionals, read the documentation for these projects.
Global Literals and Variables¶
You can define global literals and variables for templated response. This comes in handy when you have a lot of templated responses that share the same constant values or helper methods.
Literals¶
Literals are constant values. You can declare literals as follows and then reference it in templated response as {{ Literals.<literal name> }}
.
{
"data": {
...
"literals": [
{
"name":"literal1",
"value":"value1"
},
{
"name":"literal2",
"value":["value1", "value2", "value3"]
},
{
"name":"literal3",
"value": {
"key": "value"
}
}
]
}
Variables¶
Variable lets you define a helper method that can be shared among templated responses.
You can associate the helper method with a name and then reference it in templated response as {{ Vars.<variable name> }}
.
{
"data": {
...
"variables": [
{
"name":"<variable name>",
"function":"<helper method name>",
"arguments":["arg1", "arg2"]
}
]
}
{
"data": {
...
"variables": [
{
"name":"varOne",
"function":"faker",
"arguments":["Name"]
},
{
"name":"idFromJSONRequestBody",
"function":"requestBody",
"arguments":["jsonpath", "$.id"]
},
{
"name":"idFromXMLRequestBody",
"function":"requestBody",
"arguments":["xpath", "/root/id"]
}
]
}