Software Testing: Bug Reporting

In software, a bug is an error, flaw, or fault in an application. This error causes the application to produce an unintended or unexpected result, such as crashing or producing invalid results. As software testers, we deal with software bugs all the time.

Bugs have mainly been categorized on the basis of:

1. Severity: Serious bugs come under this category. These are those bugs whose functionality is crucial for the software and if that bug is not fixed then other functionality of the software will also get affected.
2. Priority: In this category, the bugs are classified on the basis of their priority which can be high or low. It is important to resolve those whose priorities are high first, from a business point of view.

Detailed categorization of bugs

• High priority, Low severity: Bug which is very important to fix but is not very severe; application name logo not displaying comes under this category.
• Low priority, High severity: Bug which don't require immediate attention and is very serious come under this category.
• Low priority, Low severity: Bugs such as spelling mistakes come under this category.
• High priority, Low severity: Bugs such as payment related issues where a customer paid the amount for some product and is being asked to pay for it again comes under this category.

Jira Workflow

1. Plan - Jira as a tool is quite handy and helps to create user stories and issues, plan sprints, and also share tasks across the software team.
2. Track - In Jira, you can evaluate, prioritise and discuss the team's work in full context with complete visibility.
3. Release - Jira always keeps the information up-to-date so that team members can ship with confidence and sanity.
4. Report - It helps in improving the team performance based on real-time, visual data that the team can use somewhere if required.

How to report a bug using Jira

1. Create an account
2. Login to Jira using your account details
3. Before reporting an issue, search for that issue, as it might have been reported already by someone else.
4. Create an issue and select the project and issue type. You will get those options after clicking on Create Issue.
5. Add the details such Summary, Priority, Components, Affected versions, Assignee, Reporter, Environment, etc.