- Installing and updating
- Navigating Postman
- Sending your first request
- Managing your account
- Syncing your work
- Discovering templates
- Creating your first collection
- Creating a workspace
- Setting up your Postman app
- Importing and exporting data
- Troubleshooting app issues
- Building requests
- Authorizing requests
- Receiving responses
- Grouping requests in collections
- Using variables
- Managing environments
- Visualizing responses
- Specifying examples
- Using cookies
- Working with certificates
- Generating client code
- Troubleshooting requests
- Scripting in Postman
- Writing pre-request scripts
- Writing tests
- Using the Collection Runner
- Scheduling runs with monitors
- Building request workflows
- Importing data files
- Working with your team
- Defining roles
- Requesting access
- Sharing your work
- Your Private API Network
- Commenting on collections
- Versioning APIs
- Using version control
- Using the API Builder
- Managing and sharing APIs
- Validating APIs
- Monitoring your APIs
- Setting up a monitor
- Viewing monitor results
- Monitoring APIs and websites
- Set up integrations to receive alerts
- Running Postman monitors using static IPs
- Troubleshooting monitors
- Monitoring FAQs
- Analyzing with reports
- Documenting your API
- Authoring your docs
- Publishing your docs
- Viewing documentation
- Using custom domains
- Publishing templates
- Publishing to the API Network
- Submission guidelines
- Managing your team
- Purchasing Postman
- Configuring team settings
- Utilizing audit logs
- Onboarding checklist
- Migrating data between teams
- Intro to SSO
- Configuring SSO for a team
- Logging in to an SSO team
- Microsoft AD FS
- Custom SAML in Azure AD
- Custom SAML in Duo
- Custom SAML in GSuite
- Custom SAML in Okta
- Custom SAML in Onelogin
- Custom SAML in Ping Identity
- Migrating to the current version of Postman
- Developing with Postman utilities
- Postman API
- Echo API
- Collection SDK
- Postman Runtime library
- Code generator library
- Postman Collection conversion
Integrating 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. This example keeps 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 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 the Newman command, but you see a failed exit code (1). Boo.
Stay calm. Let’s review the logs in Travis CI. Newman ran the tests, you see the first and second tests passed, but the last test
Updated in the last day failed.
Let’s go back to the Postman collection and fix the
Updated in the last day test.
Once you fix the mistake in the 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 the tests passed and the command exited with a successful exit code (0).
For more information about collection runs, see: