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

Integration with CI and test frameworks #385

Closed
jurisbu opened this issue Feb 22, 2016 · 3 comments
Closed

Integration with CI and test frameworks #385

jurisbu opened this issue Feb 22, 2016 · 3 comments

Comments

@jurisbu
Copy link

jurisbu commented Feb 22, 2016

Hi,

Trying to evaluate locust.io for our perf-testing needs. Have a couple questions to authors and community:

  1. I was wondering if someone has had experience integrating locust.io into Jenkins CI? Any pointers?
  2. Integration to (unit)test frameworks like nose, pytest, Behave? Anyone done that successfully?

Point 2. actually boils down to requiring test level setup/teardown hooks that would set-up system under test to a required state before test and then afterwards do the cleanup. Maybe locust.io already provides this kind of functionality?

Thanks!

@gunesmes
Copy link

You may check this post for integrating to Jenkins:

http://www.testrisk.com/2016/01/performance-testing-on-ci-integration.html?m=1

@pglass
Copy link
Contributor

pglass commented Feb 22, 2016

I run locust from jenkins. It's not exactly a fun time, but with some effort it works.

You can accomplish the basic things out of the box. You can administer locust via its api from jenkins to start and stop and the test (POST swarm and POST /stop). When the test is finished, you can fetch the response time and percentile data via the api as well, and store them wherever you like. This is fairly straightforward and gives you control to adjust the request rate (number of locust users) from a jenkins parameter.

On point two, I use the jenkins build flow plugin to orchestrate pre-test and post-test actions that run as isolated jenkins jobs. I actually deploy our locust cluster on-demand via ansible which allows me to easily reconfigure the test via job parameters in jenkins (since you need to point locust to a single file containing a single test configuration).

@jurisbu
Copy link
Author

jurisbu commented Feb 23, 2016

@gunesmes Thanks for the link!

@pglass One thing that bothered me when running locust in no-web mode was the absence of results in csv, but as you mentioned, it can be done via AP call. Not elegant, but I suppose I can make it work.

@jurisbu jurisbu closed this as completed Feb 24, 2016
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

3 participants