Bug Life Cycle Or Defect Life Cycle In Software Testing

Bug Life Cycle Or Defect Life Cycle In Software Testing

Defect life cycle is a cycle which a defect goes through during its lifetime. It starts when defect is found and ends when a defect is closed, after ensuring it’s not reproduced. Defect life cycle is related to the bug found during testing.

Click on the image for zoom view

Difference Between Severity And Priority

Difference Between Severity And Priority

Severity	Priority
Severity: It is with respect to the Impact on the functionality.	It is with respect to the impact on the business.
Example for High Severity: The Quarterly statement event is not triggering from the website and we are just at the beginning of the new quarter after a new release. In this case the Severity is High but priority could be low because we have time till the quarter end to fix the bug.	Example for High Priority: The client logo is not appearing on the web site but the site is working fine. in this case the severity is low but the priority is high because from company's reputation it is most important to resolve. After all the reputation wins more clients and projects and hence increases revenue.

Common types of computer bugs

What are the common types of computer bugs and define it ?

What are the types of bugs?

A bug could be an abstruse absurdity (code is syntactically correct, about the activated scientist or artist declared it to try to to one affair else).

• Arithmetic bugs

• Interfacing bugs

• Teamworking bugs

• Performance bugs

• Multi-threading programming bugs

• Resource bugs

• Syntax bugs

• Access violations

• Logic bugs

Testing (vs) Debugging differences between

Discuss the differences between Testing vs Debugging:

Testing

Testing activity is carried down by a team of testers, in order to find the defect in the software. Test engineers run their tests on the piece of software and if they encounter any defect (i.e. actual results don't match expected results), they report it to the development team. Along with the nature of defect, testers also have to report at what point the defect occurred and what happened due the occurrence of that defect. All this information will be used by development team to DEBUG the defect.

Debugging

Debugging is the activity which is carried out by the development team (or developer), after getting the test report from the testing team about defect(s) (you may note defects can also be reports by the client). The developer then tries to find the cause of the defect, in this quest he may need to go through lines of code and find which part of code in causing that defect. After finding out the bug, he tries to modify that portion of code and then he rechecks if the defect has been finally removed. After fixing the bug, developers send the software back to testers.

Testing vs Debugging:

Click on the image for Zoom view

What is a Software Defect, Bug and Debugging

What is a Software Defect / Bug?

A software bug is an

• Error,
• Flaw,
• Failure,
• (or) Fault