- Installation and updates
- Sending your first request
- Navigating Postman
- New button
- Creating the first collection
- Postman account
- Keyboard Shortcuts
- Troubleshooting In-app Issues
- Authorizing requests
- Working with Tabs
- Visualize API responses
- Validating Requests Against Schema
- Generate code snippets
- Using GraphQL
- Making SOAP requests
- Capturing HTTP requests
- Debugging and logs
- Troubleshooting API requests
- Intro to collections
- Creating collections
- Sharing collections
- Commenting on collections
- Managing collections
- Version Control for Collections
- Using Markdown for descriptions
- Data formats
- Working with OpenAPI
- Collaborating in Postman
- Roles and permissions
- Managing your team
- Requesting access
- Team Settings
- Audit logs
- Intro to scripts
- Pre-request scripts
- Test scripts
- Test examples
- Branching and looping
- Postman Sandbox API reference
- Intro to collection runs
- Starting a collection run
- Using environments in collection runs
- Building workflows
- Running multiple iterations
- Sharing collection runs
- Working with data files
- Debugging a collection run
- Command line integration with Newman
- Integration with Jenkins
- Integration with Travis CI
- Newman with Docker
- Documenting your API
- Authoring your documentation
- Publishing your docs
- Viewing documentation
- Custom documentation domains
- Intro to mock servers
- Setting up a mock server
- Mocking with examples
- Mocking with the Postman API
- Matching algorithm
- Intro to Monitoring
- 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
- FAQs for monitors
- Intro to Workspaces
- Creating Workspaces
- Using Workspaces
- Managing Workspaces
- Viewing changelogs and restoring collections
- The API Workflow
- Managing and Sharing APIs
- Versioning APIs
- Viewing and analyzing APIs
- Validating Elements Against Schema
- Customizing Postman
- Find and Replace
- Purchasing Postman
- 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
- Intro to Integrations
- Custom Webhooks
- Microsoft Flow
- Microsoft Teams
- Publishing 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. 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: