One of the most effective way to automate your API testing using Postman, this presentation dives deep into Postman Client, CLI and Jenkins Integration to automate the Integration Testing
2. WHY
INTEGRATION
TESTING?
Integration Testing is a level of software
testing where individual units are combined
and tested as a group.
The purpose of this level of testing is to
expose faults in the interaction between
integrated units.
4. HOW TO
PERFORM?
● Big Bang
is an approach to Integration Testing where all or most of the
units are combined together and tested at one go. This
approach is taken when the testing team receives the entire
software in a bundle
● Sandwich/Hybrid
is an approach to Integration Testing which is a combination
of Top Down and Bottom Up approaches.
5. HOW TO
AUTOMATE?
Testing APIs can be hard. Automating testing with your
CI/CD Pipeline is easy. Postman allows you to reuse
your test suites to create a CI/CD pipeline so you can
test at every push.
You can seamlessly integrate your Postman instance
with Jenkins to create your own CI/CD pipeline or add it
to your existing pipeline as a build step.
AS SIMPLE AS 1,2,3
1) Create Postman Collections with Tests
2) Integrate with Jenkins (newman)
3) Run it before your Deployment
9. NEWMAN??
Command Line Integration With Newman
Newman is a command line Collection Runner for Postman. It allows
you to run and test a Postman Collection directly from the command line.
$ npm install -g newman
$ newman run mycollection.json OR
$ newman run
https://www.getpostman.com/collections/cb208e7e64056f5294e5
DEMO (PLEASE OPEN TERMINAL)
https://learning.getpostman.com/docs/postman/collecti
on_runs/command_line_integration_with_newman/