0% found this document useful (0 votes)
7 views4 pages

Restful Booker API Testing

The document outlines various test scenarios related to booking management, including checking response codes for health checks, successful creation, and deletion of bookings. It specifies expected results for different HTTP requests such as POST, PUT, and PATCH, including conditions for successful responses and error handling. The test results indicate a mix of passes and failures, with specific status codes noted for each scenario.

Uploaded by

velatek182
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
7 views4 pages

Restful Booker API Testing

The document outlines various test scenarios related to booking management, including checking response codes for health checks, successful creation, and deletion of bookings. It specifies expected results for different HTTP requests such as POST, PUT, and PATCH, including conditions for successful responses and error handling. The test results indicate a mix of passes and failures, with specific status codes noted for each scenario.

Uploaded by

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

Scenario TID Description PreCondition

code of 201 for


1 ping health
Created check
for ping
2 health
gettingcheck
response
3 as 201 Created
Header has
4 content type
time is lessthan
5 200ms
bookings
6 successfully
Response for Get
all Booking
7 bookings are
8 deleted
booking id is
9 fetched
time is lessthan
10 200ms
able to Fetch
11 Single
Single bookings
Booking
12 Booking
When all bookings
13 are deleted
for Get Single
14 booking
able to Create
15 New resource
Successful POST
16 Request
code for successful
17 POST Request
sent has only 4 out
18 of 8 fields
only 4 out of 8
19 fields
Successful PUT
20 request
for successful PUT
21 request
code for successful
22 PUT request
partial update
23 using PUT request
Partial update
24 using PUT request
Response body for
25 PATCH request
code for successful
26 PATCH
withoutRequest
27 authorization
request body as
28 blank
failed PATCH
29 request
able to delete all
30 bookings
TestSteps Expected Result
pm.response.to.have.status(201); 4.The Status code in the
});
}); Response tab
show string asmust be 201
'Created'
}); show string as 'Created'
}); must have a content type

}); be less than 200ms


bookings
}); show list of all bookings
}); 404 for all booking deleted
}); 200 for all booking deleted

});
response body requested
response body requested
}); 3.The Response code must
}); be 404Response code must
3.The
be 200
3.The Response code must
3.Click send request button and Verify the be}200
response
pm.response.to.have.status(200); }
3.The Response code must
});
response code be
be 200
500
response code be 500

"Breakfast"
}); }
});
be 200
}); and response statuscode
}); must be 400 bad
and response request
statuscode
must be 400 bad request
request }

}); ""Breakfast,Lunch,Dinner""
PATCH request }
fail and status code must
be 403
7.Verify the status code 7.Status code must be 400
for incorrect
5.The status syntax
code must be
200
Actual Result StatusExecuted QA Name
Misc (Comments)Priority

Pass
404 Not Found Fail
Pass

pass
Automated
No

You might also like