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

Using Variables to Carry Over ID's of Responses in the Postman Collection #351

Open
paullatzelsperger opened this issue Oct 1, 2024 Discussed in #350 · 4 comments · May be fixed by #352
Open

Using Variables to Carry Over ID's of Responses in the Postman Collection #351

paullatzelsperger opened this issue Oct 1, 2024 Discussed in #350 · 4 comments · May be fixed by #352
Assignees
Labels
enhancement New feature or request

Comments

@paullatzelsperger
Copy link
Member

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

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/

@github-actions github-actions bot added the triage label Oct 1, 2024
@paullatzelsperger
Copy link
Member Author

@nikschul created an issue here. can you assign yourself?

@paullatzelsperger paullatzelsperger added enhancement New feature or request and removed triage labels Oct 1, 2024
@ronjaquensel ronjaquensel self-assigned this Oct 1, 2024
@nikschul
Copy link
Contributor

nikschul commented Oct 1, 2024

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. :)

@nikschul nikschul assigned nikschul and unassigned ronjaquensel Oct 2, 2024
@nikschul
Copy link
Contributor

nikschul commented Oct 2, 2024

@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?

@paullatzelsperger
Copy link
Member Author

paullatzelsperger commented Oct 2, 2024

I think there is currently not way to export the flows in Postman

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.

we would have to create a Postman Workspace for the repository

this gets complicated quickly and will likely involve cost etc. not likely to happen, TBH.

would you suggest to test the pre- and postscript with Postman and also to implement some integration tests for the postman collection?

Thats a good idea, maybe we just add a CI workflow that runs all requests in the "ControlPlane Management" folder using the newman tool. Basically the same thing that the TransferEndToEndTest does from JUnit. That could be done in a separate PR though.

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