You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the following steps in the yaml: steps: - name: Checkout uses: actions/checkout@v2 - name: Run Postman test scripts with Newman - Test Environment uses: matt-ball/newman-action@master with: apiKey: ${{ secrets.postmanApiKey }} collection: 15647561-02887baa-4609-40d1-a02b-3d5a2c943953 environment: 3069900-2bdc0b8d-c45t-4d41-99fa-31c0007e2a98 folder: 15647561-b5653c42-3157-5103-ab6c-d1ce39f05952
Newman runs the entire collection and fails to restrict the run to the selected folder. Prior to the test run, a "Bad object passed in config!" warning appears. The same error occurs whether using UID or folder name, and the same for folders and sub-folders.
@matt-ball I just tried passing in the stringified id of a folder containing requests. Whether I enter the id of a top-level folder or a sub-folder, the object error is gone, but none of the requests actually run.
When I pass in the name of the folder, all the requests in the sub-folder successfully run.
Using the following steps in the yaml:
steps: - name: Checkout uses: actions/checkout@v2 - name: Run Postman test scripts with Newman - Test Environment uses: matt-ball/newman-action@master with: apiKey: ${{ secrets.postmanApiKey }} collection: 15647561-02887baa-4609-40d1-a02b-3d5a2c943953 environment: 3069900-2bdc0b8d-c45t-4d41-99fa-31c0007e2a98 folder: 15647561-b5653c42-3157-5103-ab6c-d1ce39f05952
Newman runs the entire collection and fails to restrict the run to the selected folder. Prior to the test run, a "Bad object passed in config!" warning appears. The same error occurs whether using UID or folder name, and the same for folders and sub-folders.
2022-02-25T21:26:28.4480643Z ##[group]Run matt-ball/newman-action@master 2022-02-25T21:26:28.4480875Z with: 2022-02-25T21:26:28.4481318Z apiKey: *** 2022-02-25T21:26:28.4481628Z collection: 15647561-02887baa-4609-40d1-a02b-3d5a2c943953 2022-02-25T21:26:28.4481880Z environment: 3069900-2bdc0b8d-c45t-4d41-99fa-31c0007e2a98 2022-02-25T21:26:28.4482123Z folder: 15647561-b5653c42-3157-5103-ab6c-d1ce39f05952 2022-02-25T21:26:28.4482306Z insecure: true 2022-02-25T21:26:28.4482470Z color: on 2022-02-25T21:26:28.4482621Z reporters: ["cli"] 2022-02-25T21:26:28.4482785Z env: 2022-02-25T21:26:28.4482963Z APP_NAME: *** 2022-02-25T21:26:28.4483138Z NAMESPACE: *** 2022-02-25T21:26:28.4483360Z DOCKER_REGISTRY: *** 2022-02-25T21:26:28.4483787Z DOCKER_REPOSITORY: *** 2022-02-25T21:26:28.4484000Z HARNESS_APP_NAME: *** 2022-02-25T21:26:28.4484223Z ARTIFACT_SOURCE: *** 2022-02-25T21:26:28.4484487Z HARNESS_APPLICATION_NAME: *** 2022-02-25T21:26:28.4484746Z HARNESS_PIPELINE_DEV: *** 2022-02-25T21:26:28.4485013Z HARNESS_PIPELINE_TEST: *** 2022-02-25T21:26:28.4485264Z HARNESS_PIPELINE_STAGE: *** 2022-02-25T21:26:28.4485487Z PERFORM_AGAINST: *** 2022-02-25T21:26:28.4485660Z ##[endgroup] 2022-02-25T21:26:28.9440648Z ##[warning]Bad object passed in config! 2022-02-25T21:26:34.5299782Z newman
The text was updated successfully, but these errors were encountered: