Skip to content

fix(postman): always pass environmentId to runCollection for remote APIs #101

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.

Sign up for GitHub

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

Open
christosgkoros wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(postman): always pass environmentId to runCollection for remote APIs #101

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions postman/steering/steering.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ inclusion: always
- You are not allowed to use curl or any other API clients except Postman.
- A Collection ID is required
- Read the .postman.json file if it exists.
- Use the environment for local testing if it exists. An Environment ID is required
- The server must be running first
- Always pass the environment ID to `runCollection` if one is available, regardless of whether the target API is local or remote. Environment variables must be resolved for tests to work correctly.
- If the target API is a local server, ensure it is running before executing the collection. For remote APIs (e.g. staging, production, cloud endpoints), skip this check.
- After running, display a summary of the results and a breakdown by endpoint
- If any endpoint is failing, offer to investigate and fix the error
Loading