Sample Defect Report -Rest API Testing

In this tutorial, we will log a sample defect report that we might encounter during REST API testing. The bug tracker tool used is MantisBT. 

Sample Defect Report

A sample defect report provided below by invoking an API call that responds with an error.

Defect Summary:

User REST API call /createUser fails with 500 Internal server error

Reproduction Steps:

Detailed reproduction steps for the developers to reproduce the issue on the dev environment. 

Sample Steps

• Deploy User API war/ear application on the QA server.
• Start the Application server.
• Invoke the /createUser REST API call with sample data using the Rest client.
• Examine the Rest API Response.

Expected Result:

201 Created HTTP Response.

<Expected result is that the user should be created in the system by the API call. >

Actual Result:

500 Internal Server Error.

<Actual Result A server error trace is displayed.>

Defect Priority: P1

<Defect priority P1. The defect is a show stopper bug. The defect blocks testing of other API calls.

User is not created and other Restful API calls testing need a user authorization token.>

Defect Environment:

QA Environment.

API version: 2019.4.1

Rest client used like Postman tool version, User-Agent, etc.

Screenshots:

Servers Logs/ Exception Traces

We can provide the exact 500 exception trace. This information can be collected from the application server logs.

Story Point Estimate:

Measurement of complexity and/or size of a requirement. This is applicable in Agile/Scrum projects.

Bug Report

Bug report logged using Mantis Bug Tracker tool. 

Steps to create a bug report in MantisBT:

• https://www.testingdocs.com/report-an-issue-in-mantis-bug-tool/

–

Mantis Bug Tracker Tutorial:

• https://www.testingdocs.com/mantis-bug-tracker-tutorial/

Mantis Website:

• https://www.mantisbt.org/