Get Postman Scripts<\/strong><\/a><\/p>\nThis task will utilize the Postman API to retrieve the scripts your account has access to.\u00a0 This solves two troubles for us.\u00a0 We can now pull down all the scripts that the QA Team are building in the Postman Enterprise account workspaces so that we have them locally.\u00a0 This means we can easily utilize the Newman CLI task to run our scripts while still giving the QA team the ability to use their Postman Enterprise account.\u00a0 AND it gives us the added benefit of giving us a way to store those scripts in Git so that we have a good history of the scripts.\u00a0 That means if a script worked against a version of an API, and later scripts seem to be incompatible with an API, we can go back! All the benefits of source-control history for our Postman scripts can now be leveraged.<\/p>\n
My Get Postman Scripts task will require you to go in to Postman to generate a Postman API credential key token.\u00a0 This will require you to log in to your team\u2019s postman workspaces on the Postman website (I haven\u2019t found a way to do this directly through the Postman client).\u00a0 Then choose the Integrations Tab, and then Browse Integrations, and finally choose the Postman API, from there you can choose to generate an API Key.\u00a0 Keep that key safe and treat it like a password, it\u2019s your access to the Postman API for your credentials.\u00a0 Once you have that key you can enter it to the Get Postman Scripts task in your build pipeline and it should start pulling down scripts for you!<\/p>\n
How I\u2019m using this today on a team project:<\/strong><\/p>\nI have created a git Repo to hold our Postman scripts, and I have a Pipeline Build created and scheduled to run weekly for now; we will move it to run more frequently as use of Postman becomes more wide spread.\u00a0 That Build utilizes the Get Postman Scripts task to download the team\u2019s tests from Postman.\u00a0 The build also issues Git commands to keep our Git Repo up to date with the latest scripts.\u00a0\u00a0 In our release pipeline for our APIs, we utilize the Newman CLI task to execute the appropriate Postman tests against the API we released!\u00a0 There you have it, automated API testing through Postman and Newman.<\/p>\n","protected":false},"excerpt":{"rendered":"
API development is everywhere these days.\u00a0 With Microservice architectures taking off, and JavaScript frameworks needing…<\/p>\n","protected":false},"author":21,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","footnotes":""},"categories":[381,292],"tags":[385],"class_list":["post-11277","post","type-post","status-publish","format-standard","hentry","category-app-experience","category-app-innovation","tag-devops","topics-blog"],"acf":[],"_links":{"self":[{"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/posts\/11277","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/users\/21"}],"replies":[{"embeddable":true,"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/comments?post=11277"}],"version-history":[{"count":0,"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/posts\/11277\/revisions"}],"wp:attachment":[{"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/media?parent=11277"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/categories?post=11277"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/3cloudsolutions.com\/wp-json\/wp\/v2\/tags?post=11277"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}