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

Provide 'delay' option to specify delays between consecutive request #1832

Closed
ppaulweber opened this issue Aug 11, 2023 · 4 comments · Fixed by #1926
Closed

Provide 'delay' option to specify delays between consecutive request #1832

ppaulweber opened this issue Aug 11, 2023 · 4 comments · Fixed by #1926
Labels
enhancement New feature or request
Milestone

Comments

@ppaulweber
Copy link
Contributor

Problem to solve

In order to test time sensitive (related) behavioral patterns of servers hurl would need to express a "delay" in order to wait between to consecutive requests.

Proposal

Provide a TIMEOUT keyword to express on ms (or even ns) granularity a timeout about to delay consecutive requests as depicted in the following example:

POST {{LOCATION}}/endpoint
{
  "key": "value"
}

TIMEOUT 150

GET {{LOCATION}}/endpoint

Additional context and resources

This use case is related to describe more expressive and compete test/benchmark plans using combinations of the features proposed in #88 (comment)

@ppaulweber ppaulweber added the enhancement New feature or request label Aug 11, 2023
@fabricereix
Copy link
Collaborator

Hi @ppaulweber ,
we plan to add a delayoption in our [Options] section to delay the execution of the request.

POST {{LOCATION}}/endpoint
{
  "key": "value"
}

GET {{LOCATION}}/endpoint
[Options]
delay: 150

@ppaulweber
Copy link
Contributor Author

@fabricereix sounds great. So from the example you provided the semantics would be that the GET request is delayed by 150ms, right?

@ppaulweber ppaulweber changed the title Provide TIMEOUT keyword to specify delays between consecutive request Provide 'delay' option to specify delays between consecutive request Aug 11, 2023
@fabricereix
Copy link
Collaborator

exactly

@jcamiel jcamiel added this to the 4.1.0 milestone Sep 6, 2023
@jcamiel
Copy link
Collaborator

jcamiel commented Sep 6, 2023

Fixed by #1832

@jcamiel jcamiel closed this as completed Sep 6, 2023
@fabricereix fabricereix linked a pull request Sep 13, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants