Hi All, I am new to wiremock. I am trying basic mock example with decimal and I couldn't get it to work. And I dont see any example online either. Below is the response section of my json file

"response": {
    "status": 200,
    "jsonBody": {
      "weekly_rate": "{{randomDecimal lower=100.00 upper=800.00}}",
      "max_amount": "{{randomDecimal lower=5000.00 upper=20000.00}}"
    },
    "transformers": ["response-template"]
  }

and I get this response

{
  "weekly_rate": "220.87939761296946",
  "max_amount": "8860.916637737479"
}

Two issues 1. The numbers have more than 2 decimal places so the precision is not respected. 2. the numbers are strings instead of numeric

for the integer response can try this bro

"response": {
    "status": 200,
    "jsonBody": {
      "weekly_rate": {{randomDecimal lower=100.00 upper=800.00}},
      "max_amount": {{randomDecimal lower=5000.00 upper=20000.00}}
    },
    "transformers": ["response-template"]
  }

even tho the json will look like error, but it works, just try

You might need to switch to the

body

element instead of the

jsonBody

element to make sure the numeric values work.

@Gradito Tunggulcahyo I get

Unexpected character ('{' (code 123)): was expecting double-quote to start field name

To be fair,

jsonBody

can handle numeric values but not when you are using templating to generate those values. This is nothing to do with the framework, this is just basic json. Anything that makes the json invalid isn't going to work and adding

{{

to generate a numeric value is always going to be invalid json. There are many ways around this using

body

or

bodyFileName

. The random decimal precision does seem to be a limitation of the handlebars helper. I'll add an issue and see if we can do something about that for the next release.

how else to generate numeric values with jsonBody?

Looks like this should work -

{{numberFormat (randomDecimal lower=100.00 upper=800.00) '###.00' 'en_GB'}}

so like this

"jsonBody": {
      "weekly_rate": "{{numberFormat (randomDecimal lower=100.00 upper=800.00) '###.00' 'en_GB'}}",
      "max_amount": "{{numberFormat (randomDecimal lower=5000.00 upper=20000.00) '###.00' 'en_GB'}}"
    },

The

jsonBody

element won't support this as it is expecting it to be valid json. You can either switch to the

body

element like you have above or extract the body out into a separate file using the

bodyFileName

element:

{
  "request": {
    "method": "GET",
    "url": "/basic"
  },
  "response": {
    "status": 200,
    "bodyFileName": "basic.txt",
    "transformers": [
      "response-template"
    ]
  }
}

Then

basic.txt

needs to be stored in the

__files

directory and can look like this:

{
  "weekly_rate": {{numberFormat (randomDecimal lower=100.00 upper=800.00) '###.00' 'en_GB'}},
  "max_amount": {{numberFormat (randomDecimal lower=5000.00 upper=20000.00) '###.00' 'en_GB'}}
}

This should then generate a response like this:

{
  "weekly_rate": 573.97,
  "max_amount": 16922.91
}

Thank you, I will stick with body for now because lot of my other mock templates are store under mappings. I really dont get why we cannot have have a valid json spec that generates the right template. for example if the templating is designed this way

{
  "jsonBody": {
    "weekly_rate": "{{randomDecimal lower=100.00 upper=800.00 output_type='NUMERIC'}}"
  }
}

This is a valid json and the output type is clear. so its really all about how well the wiremock templating protocol is designed. I think things have to change there

No problem. I see this question on stackoverflow as well. I will add the same answers over there just in case anyone comes across that question also