Postman CLI treats skipped requests as failed

Help Hub
, ,
1

I would like to run my Postman tests in CI/CD with the ability to skip certain requests located in same collection/driectory. However Postman CLI treats requests with pm.execution.skipRequest(); as failed. Everything works fine when using manual run.

Is there any remedy to that?

image
image681Ă—447 17.3 KB

image
image579Ă—159 8.29 KB

2

Hey @adam-cimoch-d8f487b0

What’s the outcome what you run this with the Collection Runner?

4

image
image1456Ă—112 9.77 KB

image
image182Ă—620 2.76 KB

5

Do you need more info? Is it a feature? :0

6

Can you provide some more context about where you have placed this and the logic around it?

With that failed request in the CLI, what was the given reason? Are there any error messages?

7

Sure @danny-dainton

I’m running into a peculiar issue with Postman CLI and how it handles skipped requests when I specify a collection by name.

My Setup:

  • I have a Postman collection called “API”.

  • Within this collection, I have 3 folders, each containing a few requests.

  • I run a single folder at a time.

  • I provide iteration data (both via CLI and UI) which I use to determine which requests to skip dynamically via scripts.

What Works (No Issues):

  • Running a folder via the Postman UI.

  • Running a folder via the Postman CLI using folder UUIDs. In both these cases, skipped requests are handled correctly and do not cause any errors.
    postman collection run uuid-iuuid—iteration-datapath

The Problem:

  • When I run a folder via the Postman CLI using the collection name, any requests that are skipped (based on my iteration data logic) are unexpectedly treated as failed requests, even though they were never executed.
    postman collection run pathToCollection-isubFolderName—iteration-datapath

Error Message: For these skipped-but-failed requests, I receive the following error: Request could not be completed at request inside "API People/GetAllPeople"

This behavior only occurs when using the folder name located inside a collection via the CLI, not with UUIDs or the UI.

Terminal result for UUID:

image
image959Ă—620 10.7 KB

Terminal result for named -i paramter

image
image1009Ă—590 11 KB