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

Detection for runner in script #3104

Closed
1 task done
nikischin opened this issue Sep 14, 2024 · 2 comments · Fixed by #3200
Closed
1 task done

Detection for runner in script #3104

nikischin opened this issue Sep 14, 2024 · 2 comments · Fixed by #3200
Labels
enhancement New feature or request

Comments

@nikischin
Copy link

I have checked the following:

  • I've searched existing issues and found nothing related to my issue.

Describe the feature you want to add

As mentioned in #2397 I would like to have a possibility to determine wether the current request is triggered by a runner or as a single request. This will be beneficial especially when using with #2116 and a skip request function.

Usage is like this
bru.isRunner()

Returns either true or false

Mockups or Images of the feature

image
@nikischin nikischin added the enhancement New feature or request label Sep 14, 2024
@helloanoop
Copy link
Contributor

Just merged the PR #3200

New api is bru.getExecutionMode()
This will return

  • standalone - when single request is being run
  • runner - during collection runner is in progress

@nikischin
Copy link
Author

Just merged the PR #3200

New api is bru.getExecutionMode() This will return

  • standalone - when single request is being run
  • runner - during collection runner is in progress

Thank you so much @helloanoop!

Just one remark, it's req.getExecutionMode() not bru.getExecutionMode(). This does totally make sense, just not to confuse anyone passing by this ticket.

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.

2 participants