Open lcsmobileqa opened 10 months ago
Hi @lcsmobileqa I've tested this using the latest Inso and it works for all types of request chaining for me. I tested on Git repositories, exported files and Insomnia data folder and get consistent results.
Can you double-check that you are using the latest version of Inso?
I just realized that you are trying to use the environment to store the response.
This is not recommended as the environments don't re-evaluate responses and/or send requests.
My suggestion is to move from an env variable to using the Response Body
tag directly on the requests you want to use it.
Note that we are currently working a new scripting capability that will allow manipulating the environment based on the response which is probably coming on the next release.
Hi Gatzjames, thank you for your response, I really appreciate you taking the time to look into this! I tried updating the authorization tag to the response body directly in each header, but I'm still running into the same issue where it fails for inso-cli, but not the desktop. Something new that's happening is that one of my requests is running out of order--at the top of the run, instead of where it's listed in the test list. But back to what I'm seeing as far as what's reported. Here is a screenshot of the environment edited to remove that authorization token--so when I add the response body tag to the request headers, there's no confusion about where it should be pulling the value from:
Screenshot of one of the request headers showing the response body tag:
Then the setup for the response body tag:
Screenshot of the test passing in insomnia desktop:
And screenshot of the same collection run failing in inso-cli:
Not sure if this matters, but I did close and reopen insomnia desktop after making the above changes, then running it again in inso-cli, just in case that was needed for the changes to show up. I'm not sure what I'm doing differently from your setup to get this running correctly, any ideas? Anything else I should/could check on my end? Thank you again! You're a wonderful human being!
Happy to help and thanks for the kind feedback ☺️
A couple of things that will help debug this more:
inso run test --verbose
Expected Behavior
If a collection runs successfully through the desktop app, the same collection should succeed when running through the inso-cli tool.
Actual Behavior
I ran the collection with the verbose flag and got this information:
Reproduction Steps
In Insomnia Document
In Command terminal
Capture available on request.
Is there an existing issue for this?
Additional Information
Desktop app runs test suite successfully:
Inso CLI fails same test suite:
Inso CLI version:
It's whichever is installed from the Github on 11/10/2023
Insomnia Version
Version: Insomnia 8.4.5 Build date: 11/23/2023 OS: Windows_NT x64 10.0.22631 Electron: 27.0.3 Node: 18.17.1 Node ABI: 118 V8: 11.8.172.16-electron.0 Architecture: x64
What operating system are you using?
Windows
Operating System Version
Windows 11 Pro, Version 23H2, OS Build 22631.2428
Installation method
download from Insomnia
Last Known Working Insomnia version
N/A