-
Notifications
You must be signed in to change notification settings - Fork 837
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
Runner doesn't run the collection and returns error "request url is empty". #3774
Comments
I guess you are missing a step before 6, click button "Save". |
@alphabetek there is no "save" button at all. |
@alphabetek omg, sorry and thanks. Strange UI logic for me. |
This got me too. The part that tripped me up was everything else was working: sending the request, the collection, the mock server, but not the runner. So glad I found this thread, because I was stumped! |
Same here! I have to hit the save button for every request in the collection before i was able to run it. |
Solution for :Runner doesn't run the collection and returns error "request url is empty". |
Interface would be a lot more clear if the save state was somehow reflected: Color of the save button, a "last saved" timestamp, etc. |
Wasted quite a lot of time before I found this topic. This is definitely very confusing, because when you click on the request under the collection, it shows all the latest changes, even if it's not saved. I even closed Postman and reopened it and these apparently unsaved requests were still there. I just couldn't figure out why the Runner wouldn't run them. |
Same thing happened to me too. I forgot pressing save and created the monitor. |
I don't understand the use of Save logic here. The collection is always there when you close and open PostMan. |
It got me too as well :( |
Wasted tons of time before finding this. |
The UI is quite obtuse in this area. Why should whether a request is saved even have any impact on whether it can be run in the collection runner? If the request can be run using its current state in the main window it makes no sense whatsoever that it cannot be run in the collection runner. 'Save' means 'will this object's state be persisted if I close the application'. Not 'does this thing exist in all aspects of this application or only some of them (with no way of knowing which)'. And the Save button itself on the main window is totally inconspicuous and provides no feedback as to whether the request is saved or not. |
Is there an issue to improve the UI wrt the user not knowing to do an apparently superfluous save? I took a timed screenshot to capture the error and duckduckgo'd it immediately, so I only lost about 5 mins, but this appears to cumulatively cost many thousands of user hours. |
Thanks for the post |
Same here. After over 30 years in this industry it never ceases to amaze me how bad some user interfaces can be. Thanks. |
Why there is an option as selecting data file if it's gonna use the saved request anyway? |
I request the implementation of auto save. |
Thanks, saved. |
this article and solution save me in 2021. |
thank you. it saves meee. thanks a lot |
Just use, CTRL+S |
Hi guys,
App Details:
Steps to reproduce problem:
1. Add new collection "TestCollection"
2. Add new GET-request with variables
http://{{host}}/api/flight?orig={{orig}}&dest={{dest}}&dep={{depDate}}&ret=&adt={{adtCount}}&chd={{chdCount}}&inf={{infCount}}
The result link is: http://somehost/api/flight?orig=XXX&dest=XXX&dep=20171115&ret=&adt=1&chd=0&inf=0
Without any dots in domain name.
3. Add headers:
Content-Type: application/json
X-Application-Type: WebApp
4. Add environment with variables
5. Click "Send" Everything is ok.
6. Go to Collection Runner
Select the same environment, select collection, run.
Expected: response is returned.
Actually: error "Error: runtime:extenstions~request: request url is empty" in Postman console.
In DevTools:
postman_error.txt
Please tell me where I was wrong.
Many thanks.
The text was updated successfully, but these errors were encountered: