artillery is ignoring some scenario steps about artillery

[hassy]

thanks @milosgajdos! Could you throw a log in there right after the post step just to make sure the capture action is running successfully? Artillery will stop the VU by default if a capture fails, as it's likely that subsequent steps in a flow won't work anyway. Something like:

- post: {} # the post step
- log: "foo_id: {{ foo_id }}" # log
- think: 2 # rest of the flow

Also, are there any capture-related errors being reported in the summary?

[hassy]

sorry I missed the log that you also have later in the flow.

What's happening most likely is that the server is responding with something that capture can't process. It might not be returning valid JSON, or JSON in a different shape to what's expected by the JSONPath expression. You can confrm by capturing and printing the entire response:

- post:
    url: '/v1/foo'
    capture:
      json: "$" # grab the entire response
      as: full_response
- log: "{{ full_response }}"

[milosgajdos]

You can confrm by capturing and printing the entire response:

I've just done this and literally nothing is being logged 😮‍💨

[hassy]

uh oh, that doesn't sound good. Could you try re-running the test with DEBUG=http:response? (https://www.artillery.io/docs/reference/engines/http#print-response-headers-and-body) This will print every response to the terminal and should confirm whether the server isn't sending a response body back, or if there's a bug in capture.

[hassy]

I've just done this and literally nothing is being logged 😮‍💨

Also, sorry this is a 🤦 on my part. Of course the log action would not run if the capture failed. Time for a coffee.

You can also try turning off strict capture by setting strict: false attribute on it to run the rest of the steps in the flow.

https://www.artillery.io/docs/reference/engines/http#turn-off-strict-capture

[milosgajdos]

Also, sorry this is a 🤦 on my part. Of course the log action would not run if the capture failed

Ok, this is interesting...there is something strange happening in our API 🤔 I need to dig in more. Will report back! Curl calls return the json that does contain the id field, but somehow that fails intermittently which I'm guessing is causing the capture to barf which in turn prevents the next steps from running. Let me dig in more.

[milosgajdos]

Ok, false alarm, thanks for the swift answer!