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

A more involved tutorial #4

Closed
slipset opened this issue Nov 26, 2014 · 3 comments
Closed

A more involved tutorial #4

slipset opened this issue Nov 26, 2014 · 3 comments

Comments

@slipset
Copy link

slipset commented Nov 26, 2014

I'd really like to see a more involved example where the result from one request is used either as input for the next request or as a way to decide the next request.

Example:
I'd like to performance-test my web-shop application through the following scenario (assuming each step has a separate UR)L:

  1. log in
    if login ok
    2) display list of products
    3) select a random product from that list and put it in my shopping basket
    4) checkout

And I want timing on all these endpoints.

Great talk yesterday :)

@mhjort
Copy link
Owner

mhjort commented Nov 27, 2014

Great idea. To run this kind of scenario there should be a proper way to pass state between steps in a scenario. This is a basic feature in Gatling but I haven't done this yet because nobody has asked it before this. Added an issue about that. Check #5

In a meanwhile you can use atoms to workaround this. Anyway, I'll come to back to this issue when issue #5 is solved. It should not be a big deal.

@mhjort
Copy link
Owner

mhjort commented Apr 15, 2015

Better late than never. I started a series of blog posts for giving better examples. First one is out: https://medium.com/@mhjort/performance-testing-in-clojure-part-i-d75790b056e7

The first post doesn't fully cover you case but I try to get back to than in next post. (In near future that is)

@mhjort
Copy link
Owner

mhjort commented Aug 1, 2016

I'll rewrote the readme to be more elaborative a while ago. Closing this for now.

@mhjort mhjort closed this as completed Aug 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants