Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Artillery does not return with certain malformed requests #151

Open
gcuni opened this issue Mar 9, 2017 · 0 comments
Open

Artillery does not return with certain malformed requests #151

gcuni opened this issue Mar 9, 2017 · 0 comments

Comments

@gcuni
Copy link

gcuni commented Mar 9, 2017

Sometimes when capturing variables to be used in follow up calls, the capture can end up being empty for a number of reasons. If that happens, the url is empty in requestParams and the request library throws an exception that is not handled by artillery-core.
A simple fix for this can be checking that requestParams has a url before calling request(). I will submit a pull request that addresses this. This is an issue for people using this in ci/cd systems as a single bad test request can cause artillery to hang forever. Here's a simple script to repro with intentional errors in it:

config:
  target: https://aws.amazon.com
  phases:
    - duration: 20
      arrivalRate: 4

scenarios:
  -
    flow:
      -
        get:
          url: /
          capture:
            -
              json: "$.view.details"
              as: c0
        get:
          url: "{{c0}}"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant