Master/Group-Setup/Teardown

[rupeshkumar-somala-by]

It will be useful if we have grouped setup/teardown and master setup/teardown for full execution.

Currently, every thing is atomic.

Let's take an example of this . We have to do api monitoring for around 20-30 apis. I have a bearer token which is active for 15min. Here, after observing this product , i have seen setup and teardown methods which will be applicable to each single api. So, if in setup, if we get the token, we can use it and dispose it in teardown. in order to monitor 30 apis, i need to get 30 tokens everytime.

Usecase1: is there any way of this setup and teardown snippets can execute for entire, master setup and master teardown blocks available to get the token only once in master setup and once all api's are monitored , can execute master teardown to dispose it.

in next scheduled monitoring, same process will continue

Execution order: master setup > all groups (all apis) > master teardown

Usecase2: is there any way of this setup and teardown snippets can execute for grouply, grouped setup and grouped teardown blocks responsible for those grouped apis.

Execution order: group setup > all apis in that group > group teardown

[tnolet]

@rupeshkumar-somala-by thanks for contributing this. I understand the problem. Right now checks in a groups share static configuration, but run independently of each other when scheduled. The reason for this is that it reduces flakiness and possible race conditions: we keep the individual check runs as stateless and decoupled as possible.

Is there a specific issue (rate limiting or some other limit) that prohibits you from fetching the token 30 times?