Scribd
Upload
15 views

postman automation workshop

Uploaded by

allagui feten
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
15 views

postman automation workshop

Uploaded by

allagui feten
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

NEWSLETTER-

TESTING 101

1. Project creation and service import:


Introduces how to get started with
Postman by creating a collection and
how to import services using cURL.
2. Let's learn the functional flow:
Details the process of working with
booking services, including creating,
getting, updating and deleting
bookings.
3. Automation with test and pre-
request script: Focuses on test
automation by checking the status of
requests and validating specific fields
using tests and pre-request scripts.

By: Luis Carlos Rios


Chumbiauca
My name is Luis Carlos Rios Chumbiauca,
known as Lucar Panda. VISION: To focus on AI research and
Role: Professional in systems help improve people's quality of life.
. engineering, specialized in Apis.
Passion for technology: Impacted by
Artificial Intelligence (AI), he left his MISSION: To undertake, write, teach
job to research and undertake research and share knowledge about AI,
in the field becoming a valuable snowball
resource.
Postman API Automation Workshop – Basic Level

1.Project creation and import of services


1.1.We can observe the details of all the services, but today we will focus only on 4
main ones: Create, Get, Update, Delete.

1.2.The first thing we will do is open Postman and create a collection to work on this
exercise, which we will call "Test1".
1.3.Next, we will enter the link to the page with the booking services, copy the cURLs
of each service and import them into our created collection.
This should stay like this.

2. Let's learn the functional flow:


2.1.Booking reservation creation: We will send our first request, focusing only
on the first name, last name and price to create the reservation. An ID will
automatically be generated for us, which we will reserve for the next exercise.

2.2.Obtaining reservation
23.Reservation update
2.4. Reservation removal

We can see that this time the status is not 200, but 201 Created.

Remember that all the request sending results are seen at the bottom in the Body
section.
3. Automation with test and pre-request script:
3.1.For booking reservation creation, the most basic automated test in Postman is to
check the status; To do this, we will rely on snippets. We will automate by entering
the tests tab, where, on the left side, we will find the snippets and select the one
indicated for this operation.

We send the service and at the bottom we observe.

In the Test Results tab, we can verify that the status obtained from this operation,
with the expected result by invoking the snippet “Status code is 200”, is satisfactory.
The last test we will do is validate the three fields we work with: “FirstName”,
“LastName” and “TotalPrice”, invoking another snippet called “Response body: JSON
value check”.
As it is a function that requires detailed explanation, I asked chatgpt to explain it line by
line

The provided code does the following:


Define a test: pm.test("Your test name", function () {...}); defines an individual test.
Inside the parentheses of pm.test, the first argument is the name of your test, in this
case, "Your test name", which you should replace with a name descriptive of what you
are testing. The second argument is a function that contains the test code.

Extract data from response: var jsonData = pm.response.json(); gets the response of the
submitted request and converts it from JSON format to a JavaScript object, which can be
accessed and manipulated within the script. pm.response is an object that Postman provides
to interact with the request response, and .json() is a method to parse the body of the
response assuming it is valid JSON.
Make an assertion: pm.expect(jsonData.value).to.eql(100); uses the Chai.js assertions
module (via pm.expect) to check if a specific value in the response is equal to the expected
value. In this case, the value of the value property of the JSON object is expected to be equal
to 100. If the value is 100, the test passes; if not, the test fails.

To perform specific tests, we will name our tests “Verify ID Exists”, “Verify First Name
Exists”, “Verify Last Name Exists”, and “Verify Price Exists”. In addition to checking if the
value exists with a pm.expect, we will take the opportunity to save the creation results
in environment variables. This will allow us to use them in testing the remaining
services.

Before that we will create a variable taking the value of the field in the Json code, for
example jsonData.booking.firstname
To convert the json response into javascript code we use jsonData and point to the
fields in its structure.

Likewise in the pm. expect we do the same interaction by starting the taking of variables with
jsonData.

We run the test and obtain the following response:


3.2.Obtaining a booking reservation: Let us remember that, thanks to the variables saved
during the creation of the reservation, in subsequent services it will not be necessary to
enter the real value, but only to declare the variable. This avoids having to manually type
or copy and paste values.

For the url then it would look like this.


Now what we are going to do is make assertions with the values obtained in this GET
service and the values saved from the creation of the service. The code would look like
this.

To perform the comparison in pm.expect, we will create two variables:


"current_FirstName" and "expected_FirstName". "current_FirstName" will correspond
to the value obtained from the reservation obtaining service, while
"expected_FirstName" will be the variable that we store during the creation of the
reservation.

The result is like this:


3.3.Booking reservation update: Here we will use dynamic variables. For example, for
the lastname field, we will use a random variable, and for totalprice, we will assign a
variable that will use a function to return any three-digit value. For this, we will use the
pre-request script workspace.

It will be an occasion to use ChatGPT, which will help us develop a function. We must
keep in mind that, day after day, artificial intelligence becomes more relevant.
However, for today, since we are just getting started, we will use it only for the pre-
request script and automate this part of the work. As we progress through each
workshop or newsletter, we will go deeper into the use of AI. It is important to
remember that the ID in the URL will be replaced by {{variableid}}.
Using chat gpt to automate the pre request script

Now we will adapt the code for our exercise

We will replace the mention of "random number" with our variable "rndprice", which
indicates that we have programmed our function before executing the request. Next,
we will proceed to perform the test to update the price.
As usual, we will use the snippet to check the status. Now, we will proceed to
perform the assertion to confirm that the price update has been carried out
correctly.

The result is like this:

3.4.Elimination of booking reservation: To finish, we will only need a snippet of


status 201, taking into account that we will replace the ID in the URL with
{{variableid}}.
It is important to remember that all test results are displayed at the bottom, in the
Test Results section.

You might also like