Execution sequence of 'Script' and 'Tests' blocks at the collection level and request level - inconsistent between UI app and CLI #2617
Labels
bug
Something isn't working
Comments
|
Folder level scripts, variables, etc are not implemented in CLI. The inital PR also does no real changes to the CLI: #2529 |
|
I just ran into this today. I defined a variable (that holds the schema definition for a response) in each request. The variable is referenced in the folder script and validated via Ajv -- this works since the request script is run first, its a way of "passing" the schema to the folder level validation. It works great in the UI, but sadly does not run the validation logic via CLI (since it's folder level script). Hoping the CLI gets updated to parity with the UI! Edit: here is a PR that addresses this issue: #3049 |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have checked the following:
Describe the bug
With reference to an earlier reported issue #2597, we (@hbrahi1) understand that the new execution sequence is now the "Sandwich Flow" (Thank you @Its-treason for clarification).
However, we further notice that this execution sequence is inconsistent between the UI app and CLI. The app seems to be using the (new) "Sandwich Flow' while the CLI uses the (previous) "Normal Flow". We believe both should be consistent with each other.
.bru file to reproduce the bug
Test collection 'Bruno Execution Sequence' to reproduce the above-reported bug (by running in the app vs CLI):
Bruno Execution Sequence.zip
Screenshots/Live demo link
Bruno Execution Sequence in UI app v1.20.4:
Bruno Execution Sequence in CLI v1.20.4:
The text was updated successfully, but these errors were encountered: