-
Notifications
You must be signed in to change notification settings - Fork 172
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
Using Variables to Carry Over ID's of Responses in the Postman Collection #351
Comments
@nikschul created an issue here. can you assign yourself? |
I don't think I currently have the permission to assign myself, but I am currently working on the issue. Therefore my colleague @ronjaquensel assigned herself for now. :) |
@paullatzelsperger regarding the Postman Flows: I think there is currently not way to export the flows in Postman (https://community.postman.com/t/export-postman-flow/60756/3), so I guess we would have to create a Postman Workspace for the repository in order to share flows or do you see another option? regarding software tests: would you suggest to test the pre- and postscript with Postman and also to implement some integration tests for the postman collection? |
yeah, seems that way. we'll have to hold off on that, but maybe we could document that possibility in the README somewhere, like "hey, you can either follow the sequence in this document, or you define a flow to chain together the requests" and an explanation on how to do it.
this gets complicated quickly and will likely involve cost etc. not likely to happen, TBH.
Thats a good idea, maybe we just add a CI workflow that runs all requests in the |
Discussed in #350
Originally posted by nikschul October 1, 2024
Currently - when executing the REST requests inside the Postman collection in the order described in step 7 of the README.md - some IDs of previous responses have to be copied over manually to the next request. Even though this could have a certain learning effect for new users as they have to understand which ID has to be used when, this could also be simplified by automating it with Postman variables.
Here is an example:
![image](https://private-user-images.githubusercontent.com/178764556/372347504-11c08c31-c161-4cb5-b2dc-ca4a1c977a69.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzYzMzA3ODEsIm5iZiI6MTczNjMzMDQ4MSwicGF0aCI6Ii8xNzg3NjQ1NTYvMzcyMzQ3NTA0LTExYzA4YzMxLWMxNjEtNGNiNS1iMmRjLWNhNGExYzk3N2E2OS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMTA4JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDEwOFQxMDAxMjFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT02ZWE0ZDQ1NmUwMzEzMzVhNjk1Y2YwYWI4OGE3NWNjNmQwYThlODM4YTVhNTBkODUwMjQxZDZhYjcyNzk5NGRlJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.YjA6kXh76spDxDV6JrHESgM1gk7gyyF-raAe8nAf9FY)
Instead of manually copying the "contractAgreementId" over to the next request, it could be automatically carried over to the next request.
This could be accomplished with post-request scripts: https://blog.postman.com/extracting-data-from-responses-and-chaining-requests/
The text was updated successfully, but these errors were encountered: