Driving Pipeline Automation With Newman and the Postman API
summary
Shows how to run Postman collections from CI/CD using Newman CLI and the Postman API to fetch live collections and environments instead of checking in JSON blobs. Demonstrates a Jenkins-backed deployment triggered by a Slack bot that runs tests, reports one failed out of eight, fixes a milliseconds-vs-seconds assertion, retags a collection snapshot, and reruns to pass. Recommends tagging snapshots for deterministic runs and adding observability and monitors around pipelines.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:58How did we get here
- 3:29Extreme Programming
- 4:37Continuous Integration
- 5:44Unified Development
- 7:12Tools
- 8:02Cloud Hosted Assets
- 9:17Running Locally
- 9:31What is Newman
- 10:36Newman reporters
- 11:22Export collections
- 12:00Get from API
- 13:49Workflows
- 14:17Postman App
- 14:41API Entity
- 25:21QA
- 25:51Process Design
- 27:10Building Automation
- 28:46Questions
related talks
34mPostman & Newman for your CICD
16mAutomation API Testing
22mRevolutionizing API development: Collaborative workflows with Postman
35mMastering API Ops: Build Scalable Applications
20mDocker Extensions Show and Tell
39mRemove your Testing Bottleneck with CI/CD Pipelines
28mOptimizing the developer experience through collaboration
36mUsing Jenkins to Build, Deploy, and Automate Projects