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

Failure Control #1033

Closed
rahul-jain101 opened this issue Jun 24, 2019 · 1 comment
Closed

Failure Control #1033

rahul-jain101 opened this issue Jun 24, 2019 · 1 comment

Comments

@rahul-jain101
Copy link

Is there a way to control what Locust counts as a failure rather than checking HTTPSession client's status code? Just wondering because currently I have implemented my own custom HTTP client with all the REST calls and more in my class called risk and I have assigned client to be an instance of risk, but some of the methods in my risk class do not have an implicit status code associated with them while other methods do. I would like to control how Locust counts certain methods as failures, I don't want it checking the status code each time, also if an exception happens or a timeout, does that count as a automatic failure?

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

2 participants