DIFFERENCE BETWEEN DEFECT , BUG, ERROR AND FAILURE

DIFFERENCE BETWEEN DEFECT , BUG, ERROR AND FAILURE 




DEFECT:

If  difference exist  between actual result and expected result  and that difference is found by developer and corrected by himself in the development phase then it’s called a defect. 


 Example if developer has developed a code  and while performing (Unit Testing) developed found that the code is not functioning as per requirement then in tat case the issue occurred is known as DEFECT.

BUG:

If testers find any mismatch in the application/system in testing phase then they call it as Bug. Example if the developer has done the development  and performed Unit testing of a login form then the module is sent to Tester for performing testing. In this phase if tester found that the client requirement is not matching with the  result of application then tester report it as Bug. 

NOTE:  there is a contradiction in the usage of Bug and Defect. People widely say the bug is an informal name for the defect.

ERROR

If we can’t compile or run a program due to coding mistake in a program. If a developer unable to successfully compile or run a program then they call it as an error.

Example: A developer may misunderstand a de-sign notation, or a programmer might type a variable name incorrectly — leads to an Error. It is the one which is generated because of wrong login, loop or due to syntax. Error normally arises in software; it leads to change the functionality of the program.

Failure:

Once the product is deployed and customers find any issues then they call the product as a failure product. After release, if an end user finds an issue then that particular issue is called as failure.

Comments

Post a Comment

Popular posts from this blog

SOFTWARE DEVELOPMENT LIFE CYCLE MODELS (SDLC MODEL)

Image
A software life cycle model is a descriptive representation of the software development cycle. SDLC models might have a different approach but the basic phases and activity remain the same for all the models. 1) Waterfall Model 2) V-Shaped Model 3) Prototype Model 4) Spiral Model 5) Iterative Incremental Model  6) Big Bang Model 7) Agile Model Waterfall Model The  Waterfall Model  was the first Process Model to be introduced. It is very simple to understand and use it. In a  Waterfall  model, each phase must be completed before the next phase can begin and there is no overlapping in the phases.  The waterfall  model is the earliest  SDLC   approach that was used for software development. n “ The Waterfall ” approach, the whole process of  software development  is divided into separate phases. The outcome of one phase acts as the input for the next phase sequentially. This means that any phase in the development process begins only if the previous phase is complete. The waterfall model
Read more

Software Testing Life Cycle (STLC)?

Image
STLC(SOFTWARE TESTING LIFE CYCLE) It is a sequence of specific activities conducted during the testing process to ensure software quality goals are met. STLC involves both verification and validation activities. Contrary to popular belief, Software Testing is not just a single/isolate activity, i.e. testing. It consists of a series of activities carried out methodologically to help certify your software product. STLC stands for Software Testing Life Cycle. PHASES OF STLC : Requirement Analysis Test Planning Test case development Test Environment setup Test Execution Test Cycle closure What is Entry and Exit Criteria? Entry Criteria:  Entry Criteria gives the prerequisite items that must be completed before testing can begin. Exit Criteria:  Exit Criteria defines the items that must be completed before testing can be concluded. Requirement Analysis During this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may in
Read more