Passing request body from json file to artillery api tests.

[BhavnaSoni1991]

I want to add performance tests for api having quite complex request payload and hence want to pass them through json file. Does artillery support reading request payload from json file? In the examples I could see request payload values are directly passed in yml file and not read from any file.

[bernardobridge]

Hi @BhavnaSoni1991 👋

IMO the easiest way to do it is to use a custom javascript function, where you can require the JSON file and then set the body directly to it:

processor.js

const myJson = require('./path-to-json');

function setJSONBody(requestParams, context, ee, next) {
  requestParams.body = JSON.stringify(myJson);

  return next();
}
module.exports = { setJSONBody };

Then, you can call that in a beforeRequest (or beforeScenario) hook.

config:
    ...
    processor: './processor.js'
scenarios:
  - flow:
      - post:
          url: '/'
          beforeRequest: "setJSONBody"

[BhavnaSoni1991]

Thanks @bernardobridge the solution worked!!

[BhavnaSoni1991]

Hi @bernardobridge my script ran file on local using the code snippet above but in the gitlab pipeline I am getting following "MODULE_NOT_FOUND" error when trying to run on aws fargate.
I suspect that this is related to require module. Can you please help?

[bernardobridge]

Hi @BhavnaSoni1991 , I would need more details:

• actual full error stack you saw
• your file structure
• did the list of files that Fargate lists in the beginning include your json?

[BhavnaSoni1991]

@bernardobridge I figured out that my json file is not being listed in AWS fargate Test bundle contents. I have kept this json file under resources folder. Do I need to do anything explicitly so that fargate lists it?

[bernardobridge]

Hi @BhavnaSoni1991 , the json file should be automatically detected by the Test bundle, so that might be a bug. Unfortunately, without more information, I cannot debug this. Can you please provide:

• Your full file structure (your scenario, config, processor and json, and their locations)
• The contents of your test yaml, and the processor file

Thanks!

[BhavnaSoni1991]

hi @bernardobridge below is the full file structure of my scenario file(test3.yml), config is same yml file (test3.yml), processor (helper.js), json (test3.json) file.

Below are the contents of yaml file and processor file

Could you please have a look and let me know what is wrong?

[BhavnaSoni1991]

hi @bernardobridge does the path have to be given differently in includeFiles since I am trying to pass path same way I have done for processor and path below. I can now see the fargate is bundling the json but it is taking incorrect path?

[bernardobridge]

The requestPath you've set in this case is relative to the processor file, since you are requiring it dynamically from the processor file.

The path you set in includeFiles needs to be relative to the config.

[BhavnaSoni1991]

Thank you so much @bernardobridge for your quick response it worked !!

[BhavnaSoni1991]

hi @bernardobridge until now the solution described above worked for single virtual user. Now I am trying to execute the same for multiple virtual users which means I have to change the unique value in request payload for each virtual user. Since as of now I am setting request body using setJSONBody method as described above to which I was passing json file path and request key. Now in addition to that I also need to change some value of request payload? Could you please help me how can I achieve it using setJSONBody method?

[roydekleijn]

Have you found a solution for this?