Most important steps to create a new bugs in software testing

40

whenever we are testing any software or any website There are mostly 10 important steps we should needs to remember as a tester .

1- Summary

In this phase we need to create a perfect summary for any bug in which we should need to mentioned a reason of bug in very few words so that developer can easily understand the problem.

2- Description

In this phase as a tester we should need to explain each and every important detail related bug why this bug occured reason behind bug and steps of bug , we need to explain everything in description so that developer can easily understand the issue and for future uses also anyone can understand easily.

3-Expected Result

In this phase of bug we set expected result of that particular bug as per the requirements we have, In this we mentioned what expectation we have from particular website/software.

4- Actual Result

In this phase of bug we compare test case actual result with our expected result and based on that result we understand the problem, If actual result and expected result both are same as per requirements then the test case will be passed and if actual result is not same as expected then as a tester we will show a status of that test case as failed.

5-Severity

Bug Severity or Defect Severity in testing is a degree of impact a bug or a Defect has on the software application under test. A higher effect of bug/defect on system functionality will lead to a higher severity level. A Quality Assurance engineer usually determines the severity level of a bug/defect.

Types of Severity

In Software Testing, Types of Severity of bug/defect can be categorised into four parts :

  • Critical: This defect indicates complete shut-down of the process, nothing can proceed further
  • Major: It is a highly severe defect and collapses the system. However, certain parts of the system remain functional
  • Medium: It causes some undesirable behavior, but the system is still functional
  • Low: It won’t cause any major break-down of the system

6- Priority

Priority is defined as the order in which a defect should be fixed. Higher the priority the sooner the defect should be resolved.

Types of Priority of bug/defect can be categorised into three parts :

  • Low: The Defect is an irritant but repair can be done once the more serious Defect has been fixed
  • Medium: During the normal course of the development activities defect should be resolved. It can wait until a new version is created

High: The defect must be resolved as soon as possible as it affects the system severely and cannot be used until it is fixed.

7-Logs/Attachments

There are three types of attachments:

  • Video file;
  • Logs;

Screenshots.

Mainly as a software tester we takes screenshot to show a bugs in application/website,with the help of screenshot we will show the exact issues to developers or other team members.

The screenshot is a digital photo of the display that is created with a built-in functionality of OS or some other special program. It is better to attach screenshots using the formats like «.png», «.bmp», «.jpeg». They are generally available. Hence, you can analyse the screenshot without installing additional programs.

8-Sprint

Sprints are time-boxed periods of one week to one month, during which a product owner, scrum master, and scrum team work to complete a specific product addition. During a sprint, work is done to create new features based on the user stories and backlog. A new sprint starts immediately after the current sprint ends.

9-Label

In this phase as a tester we will show that in which functionality actually we facing problem when we compare actual and expected results.

10-Types of the bug

7 types of software bugs and errors
  • Functional errors. This is a broad type of error that happens whenever software doesn’t behave as intended. …
  • Syntax errors. …
  • Logic errors. …
  • Calculation errors. …
  • Unit-level bugs. …
  • System-level integration bugs. …
  • Out of bounds bugs.

 

 

Click here to read in hindi