Lesson 02 Collections
Lesson 02 Collections
Collections
A Day in the Life of an Automation Testing Engineer
After completing this session, John will be able to create and run a
Collection in Postman.
Learning Objectives
Define a Collection
• Create folders
• Insert similar requests into a folder
• Run multiple requests at a single click
• Run subsequent requests
• Create easy API Documentation
Why a Collection Is Used?
Why a Collection Is Used?
The Collection does not provide a response body for each request after execution.
The Collection Runner console generates a status for every request, pass or fail.
A Collection Runner must have at least two requests for the Collection.
The Collection Runner also contains information on the response code, time, payload size,
and checkpoints. Results are displayed in green for passes and red for failures.
How to Share a Collection?
Sharing a Collection
Users can send links to the Collections from the Postman app to those who are not on the workspace
team. They can also send the Collections directly to the team. Users must be signed in to share a
Collection on Postman.
Shared as a file
How to Remove a Collection from
Workspace?
Removing a Collection from Workspace
Users can execute a Postman Collection directly from the command line using Newman.
Users can use Newman to run Collections in the same manner that a Postman Collection
Runner does.
Continuous integration by Newman in Postman makes this combination of tests and code
successful and enables users to merge the various codes and run the tests continually.
Advantages of Using Newman
It utilizes
the Newman
It offers test It can conduct
command-line tool
suites that are Instantaneous
to integrate with
simple to make. testing.
build systems,
It allows keeping It can quickly
such as Jenkins.
data needed to transfer
conduct tests Environments and
in various tests to code
Environments. repositories.
Key Takeaways