- Installation and updates
- Sending the first request
- Creating the first collection
- Navigating Postman
- Keyboard Shortcuts
- Postman account
- New button
- Troubleshooting In-app Issues
- Customizing Postman
- Find and Replace
- Troubleshooting API requests
- Debugging and logs
- Capturing HTTP requests
- Interceptor extension
- Generate code snippets
- Making SOAP requests
- Working with Tabs
- Using GraphQL
- Visualize API responses
- Intro to collections
- Creating collections
- Sharing collections
- Managing collections
- Using Markdown for descriptions
- Data formats
- Working with OpenAPI
- Commenting on collections
- Version Control for Collections
- Intro to scripts
- Pre-request scripts
- Test scripts
- Test examples
- Branching and looping
- Postman Sandbox
- Postman Sandbox API reference
- Intro to environments and globals
- Manage environments
- Manage globals
- Variables complete reference
- Dynamic Variables List
- Intro to collection runs
- Starting a collection run
- Using environments in collection runs
- Working with data files
- Running multiple iterations
- Building workflows
- Sharing a collection run
- Debugging a collection run
- Command line integration with Newman
- Integration with Jenkins
- Integration with Travis CI
- Newman with Docker
- Intro to API documentation
- Viewing documentation
- Local environments and shared environments
- How to document using Markdown
- Publishing public docs
- Adding and verifying custom domains
- Adding team name and logo
- Intro to Monitoring
- Setting up a monitor
- Viewing monitor results
- Monitoring APIs and websites
- Set up integrations to receive alerts
- Pricing for monitors
- Troubleshooting monitors
- FAQs for monitors
- Intro to mock servers
- Setting up a mock server
- Mocking with examples
- Mocking with the Postman API
- Matching algorithm
- Introduction to APIs
- Managing APIs
- Sharing APIs and managing roles
- The API Workflow
- Versioning APIs
- Reporting FAQs
- Viewing and analyzing APIs
- Intro to Workspaces
- Creating Workspaces
- Managing Workspaces
- Using Workspaces
- Sharing collections in Workspaces for version 5
- Activity feed and restoring collections
- What is Postman Pro
- Purchasing Postman Pro
- Billing and pricing
- Upgrading to Postman Pro from a trial team
- Team Settings
- Changing your plan
- Managing your team
- Migrating to Postman v7
- Roles and permissions
- Managing your billing
- Intro to Enterprise
- Purchasing Postman Enterprise
- Running Postman monitors using static IPs
- Intro to SSO
- Configuring SSO for a team
- Logging in to an SSO team
- Configuring Microsoft AD FS with Postman SSO
- Setting a custom SAML in Azure AD
- Setting up custom SAML in Duo
- Setting up custom SAML in GSuite
- Setting up custom SAML in Okta
- Setting up custom SAML in Onelogin
- Setting up custom SAML in Ping Identity
- Audit logs
- Public API documentation
Integration with Travis CI
Continuous Integration (CI) is a practice that requires developers to integrate code in a shared repository several times a day.
By committing early and often, the team avoids a ton of technical debt by allowing teams to detect problems early while conflicts are relatively easy to fix.
Every check-in triggers an automated build process that typically includes testing. And if your commit hasn’t broken anything, might include deployment too.
You will set up your CI configuration to run a shell command upon starting your build. The command is a Newman script that runs your collection with the tests, returning a pass or fail exit code that’s logged in your CI system.
In this example, we’ll walk through how to integrate Postman with Travis CI, a continuous integration service that builds and tests projects on GitHub.
Travis CI runs your tests every time you commit to your GitHub repo. Then it submits a pull request, or some other specified configuration.
Let's learn more about integration with Travis:
- Select a Postman collection with tests: For now, let’s assume you already have a Postman collection with tests. Download the sample collection and environment by clicking the Run in Postman button if you want to follow this example.
- Set up a GitHub repository: Travis CI is free for open source projects on GitHub. In this example, we keep our Postman tests in a public GitHub repo.
Set up Travis CI: Follow the Travis CI getting started guide for the complete walk through.
Sign in to Travis CI with your GitHub account.
Go to your profile page and enable Travis CI for the public GitHub repo we set up in the previous step.
Export the Postman Collection as a JSON file and move the file to your project directory. If you’re using an environment such as this example, download the Postman environment as a JSON file and move the file to your project directory as well.
In this example, we've moved both files into a directory called
testsplaced in the root of the project repository.
Remember to add and commit these two files to your repo.
Create a new file called
.travis.ymland move it to the root of your project repository.
Remember to add and commit it to your repo. This file tells Travis CI the programming language for your project and how to build it.
Any step of the build can be customized. These scripts will execute the next time you commit and push a change to your repo.
.travis.ymlfile, add a command to
installNewman in the CI environment, and then add a
scripttelling Newman to run the Postman tests (which we've placed in the
Since Travis CI doesn’t know where Newman is located, let's update the
PATH. In this node.js example, the
newmantool is located in my
.bindirectory which is located in my
.travis.ymlfile looks like this for this
language: node_js node_js: - "8.2.1" install: - npm install newman before_script: - node --version - npm --version - node_modules/.bin/newman --version script: - node_modules/.bin/newman run tests/bitcoinz.postman_collection.json -e tests/tests.postman_environment.json
Travis CI is now set up to run your Postman tests every time you trigger a build, for example, by pushing a commit to your repo.
Let’s try it out. The Travis CI build status page will show if the build passes or fails:
Travis CI is running our Newman command, but we see a failed exit code (1). Boo.
Stay calm. Let’s review the logs in Travis CI. Newman ran our tests, we see the first and second tests passed, but the last test
Updated in the last day failed.
Let’s go back to our Postman collection and fix our
Updated in the last day test.
Once we fix the mistake in our test, let’s save the changes, update the repo with the latest collection file, and then trigger a Travis CI build once again by committing and pushing the change.
And it's working! All our tests passed and the command exited with a successful exit code (0).
For more information about collection runs, see: