Definition of Bug, Defect or Issue | Element and Live example of bug, defect or issue

Definition of Bug, Defect or Issue

Here in this section we will discuss about the software or application issues found in testing. Issues are also known as bugs, faults or defects etc..

Live example of bug, defect or issue:

i.                    While executing the test cases, there are high possibilities to find the difference in result in between the Actual result and estimated result. This difference is known as bug and also called the defect or issue.

ii.                  After finding the bug next important step is reporting the bug to developer. Now how you will explain the bug to developer and what information is required with bug. All these points are provided below or what a bug report should contain.

Element of Testing Report:

iii.                Bug ID: This is the serial no of bug, this will always unique.

iv.                Bug Description: Here all details of bug will be provided means, related module, test data etc.

v.                  Version of Application: Version of application should mention properly, in which version you find the bug.

vi.                Steps to Generate the Issue: Steps should be explained properly in report with all possible screenshots so that developer can understand and easily generate the issues to fix.

vii.              Bug generated date: Date should be motioned clearly when the bug was generated.

viii.            Reference: All type of reference should be clear, i.e. screen shot, test data or any other related module etc. So that developer can easily understand the issue.

ix.                Detected or Tested By – Proper name or id should be mentioned in report who has been perform testing on that module.

x.                  Developed by – Developer name should also explained in report.

xi.                Severity – show the impact of bug on application, high severity mean high impact and low severity mean low impact.

xii.              Priority – show the requirement of fix the issue mean how much it required to fix. Severity and Priority can be High / Medium / Low. Like a bug can be of high priority and low severity OR high severity or low priority.

Software Testing Principle	Software Development Life Cycle	Unit Testing
Integration Testing	System Acceptance Testing	Sanity and Smoke Testing
Regression Testing	Non Functional Testing	Test Case
Test Scenario	Software Testing Rules	SQL For Software Testing
Test Case Design and Example	Test Base	Traceability Matrix
Boundary Value analysis	Decision Table in Software Testing	State Transition Definition
Use Case Testing	Testing Review	Techniques of Test Estimation
Test Plan Structure	Definition of Bug	Bug Life Cycle
Automation Testing Tools	Test Web Based Application	Software Testing Types
Software Testing Techniques	Techniques in Software Testing	Test Data
Software Testing Life Cycle	Black Box Testing	Difference between Black Box testing and White Box Testing
Smoke and Sanity Testing	Testing Methodology	Extreme Programming
White Box Testing	System Software Testing	Performance Testing
Usability Testing	User Acceptance Testing	Regression Testing
MANUAL SOFTWARE TESTING	Automation software Testing	Functional Testing

definition of bug, defect or issue, content of testing template, element of testing report, live example of bug, defect or issue, priority and severity of issue bug defect.

MOBILE APPS    QTP TESTING QUESTIONS  MANUAL TESTING  ANDROID APPS