-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
New Feature: Post Pesponse for both "before request" and "after request" #2680
Comments
I feel like this would overcomplicate things. The better (and already planned) solution was to have a toggle Sandwich & natural flow on collection level: #2639 |
Hi @Its-treason, thanks for your reply. I rethink my feature request and edited it. The advantage of having both also is that at collection/folder level I can define generally used functions on one hand and on the other the after having the response at collection/folder level I can decide how to continue with the conditional workflow. Kind Regards |
- Adds a new key in the `bruno.json` under `scripts.flow` - When concating post and tests scripts the flow will now be used to determine to correct order Fixes: usebruno#2648 usebruno#2680 usebruno#2597 usebruno#2639
- Adds a new key in the `bruno.json` under `scripts.flow` - When concating post and tests scripts the flow will now be used to determine to correct order Fixes: usebruno#2648 usebruno#2680 usebruno#2597 usebruno#2639
I have checked the following:
Describe the feature you want to add
Hi,
I have read #2597 which clarified the situation of execution sequence of scripts at different levels: collection folder, request.
Unfortunately the current sandwich flow almost make it impossible to import a Postman collection without massive changes. All tests at collection or folder level must be duplicated to the requests. Doing so will result in a working but unmaintainable collection.
So I want to get a separation of "Post Response" and "Tests" in to different sections: before request and after request
Following my idea will meet all requirements:
------------ insertion on 20240723 start
The reason for having both "before request" and "after request" is that i plan:
------------ insertion on 20240723 end
The following diagram illustrates the execution sequence:
Kind regards
Thomas
Mockups or Images of the feature
For Folder an Collections the dialog can look like these:
The text was updated successfully, but these errors were encountered: