Bug Reporting and Issue Tracking

QA Team’s guideline when reporting bugs and tracking its progress.

Bugs should be verified more than once using the same environment before being reported.

Tickets should have the following information:

Summary

Environment

Credentials

URL

Pre-Condition

Detailed steps on how to replicate the bug.

Screenshots (IMPORTANT)

How to report a bug?

JIRA:

Sample Bug Report

Summary: “XYZ: SSO: Single Sign-on (SSO) login is not working.”

Environment: Production

Credentials: “sso-login@gmail.com/1234qwer”

URL: https://www.testapplication.com.au

Prerequisite:

SSO account should be available.

Steps:

Go to URL.

Click Sign in button.

Input credentials.

Click Login button.

Check behavior.

Current: User is not able to Login.

Expected: User should be able to login using SSO credential.

ALWAYS ADD SCREENSHOTS.

Defect Severity

Indicates how damaging is the bug/issue encountered.

Blocker/Critical (Highest) - mission critical to the core functionality of the application and for which there are no workarounds.

Major (High) - related to the core functionality of the application, but don’t have to be fixed before product launch. However, these bugs should be fixed in the first available patch or release after launch.

Medium - does not affect any critical user functionality. Typically, these bugs have workarounds that allow users to accomplish the desired task that the bug may have hindered or the function may still operate but in a degraded fashion.

Low - these bugs do not interfere with core functionality and are just annoyances that may or may not ever be fixed.

Defect Resolution (TO BE REVISED)

⁠

Ticket Status

To Do are tickets that are not being worked on yet.

In Progress are tickets with assigned team member already working on the ticket.

For Code Review are tickets that are done developing and needs to be reviewed by another developer.

For QA review are tickets that passed the Code Review and ready for QA Testing.

Change Requested are tickets that failed the Code Review or QA Review.

Done are tickets that passed the QA review.

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.