Nice video, I have a bunch of questions (other viewers feel free to answer if you know): 1) How do you get the name of the target collection you want to generate the Postman assets? (It would be useful to put this command in the description of this video.) 2) How does newman know to query the endpoint on localhost:8000? What if the server is on a different port? 3) Do you need to do anything to set up your Postman workspace prior to running the newman command? At 3:00 you already have collections for Client Smoke Tests, Docs, and Mocks. Do these need to exist before? I have a completely brand new workflow (I haven't used many features in Postman outside of one-off requests.) 4) Why would you want to write documentation specific to Postman? Wouldn't this be more useful in the source code of the FastAPI app? Can the collection pull documentation from the API spec instead? It would be great to see a follow-up video that goes further into the other features like managing smoke tests and mocks. I've never used these features so its all new to me. Cheers
hi @greg! thanks for the questions! 1-3 are covered in my new video, th-cam.com/video/2wBW3nEdBqk/w-d-xo.html for number 4, you could definitely do this in fastapi / elsewhere in the api lifecycle. happy to chat more, for some companies different groups own the documentation / portal vs the api spec / code
🚀 and the latest update to this solution makes it much easier and clearer to determine / set up the ID’s and URL you asked about. we appreciate your feedback!
Nice video, I have a bunch of questions (other viewers feel free to answer if you know):
1) How do you get the name of the target collection you want to generate the Postman assets? (It would be useful to put this command in the description of this video.)
2) How does newman know to query the endpoint on localhost:8000? What if the server is on a different port?
3) Do you need to do anything to set up your Postman workspace prior to running the newman command? At 3:00 you already have collections for Client Smoke Tests, Docs, and Mocks. Do these need to exist before? I have a completely brand new workflow (I haven't used many features in Postman outside of one-off requests.)
4) Why would you want to write documentation specific to Postman? Wouldn't this be more useful in the source code of the FastAPI app? Can the collection pull documentation from the API spec instead?
It would be great to see a follow-up video that goes further into the other features like managing smoke tests and mocks. I've never used these features so its all new to me.
Cheers
hi @greg! thanks for the questions! 1-3 are covered in my new video, th-cam.com/video/2wBW3nEdBqk/w-d-xo.html
for number 4, you could definitely do this in fastapi / elsewhere in the api lifecycle. happy to chat more, for some companies different groups own the documentation / portal vs the api spec / code
🚀 and the latest update to this solution makes it much easier and clearer to determine / set up the ID’s and URL you asked about. we appreciate your feedback!
This is so cool - exactly what I wanted for my side project
Nice walk-through!!
what is this json viewer chrome extension?
Wonderful my life.
thanks to you
Ty