SDET Unicorns

Run Postman Tests on Travis CI

Table of Content

One of the great features of Postman is that it is really easy to integrate it with CI/CD tools like Travis CI, Jenkins, etc… In this post, we will take a look at how to run Postman tests on Travis CI.

Initial Setup

To get the tests running on Travis CI, you’ll need to do some initial setup –

  • Create a GitHub Repository and push collection and environment related files to GitHub
  • Connect your GitHub repository with TravisCI

Creating .travis.yml file

Once GitHub and Travis is connected, you can focus on creating the Travis configuration file which will look something like this –

language: node_js
node_js:
  - '14.4.0'

install:
  - npm install newman

script:
  - node_modules/.bin/newman run tests/Trello.postman_collection.json -e tests/Production.postman_environment.json

Once you push this file to GitHub, Travis will pick up the configuration file and start building your project and run all your tests in your collection.

Travis Postman Tests Run

Check out the video below to learn more about Postman Travis integration –


To learn about API Test Automation using JavaScript, check out my free tutorial series here –

JavaScript API Test Automation Tutorial Series


I hope this post helped you out, let me know if you have any questions in the comments below!

Happy testing! 

My Resources

Thrive Suite: The all-in-one WordPress theme I used to create my blog.
Jasper AI: My favorite AI writing tool.
Surfer SEO:  A tool to help you rank your content on the first page of Google.

Write Content Faster

5/5

Write blog posts that rank for affiliate terms!

Join our mailing list

Unlock the Secrets to Becoming a SDET Pro in the Industry!

Stay ahead of the curve! Join our mailing list for exclusive insights, tips, and the latest industry updates delivered straight to your inbox

Table of Content

Related Post

Functional vs Regression Testing

Functional Testing vs Regression Testing: Main Differences

Testing has increasingly become a requirement in the software development lifecycle in recent years. The realization that development is no longer a focal point for stakeholders but saving costs by catching defects early in their application makes it necessary to learn different testing types.

Read More »