concept of bug, defect, error, failure, fault,

-

Bug, Defect, Error, Fault & Failure?  


  • Defects are the variance between actual and expected results.  
  • A mistake in coding is called Error and error found by the tester is called Defect.  
  • The defect accepted by the development team then it is called Bug.  
  • The build product does not meet the client requirements, then it is called Failure.

 

What is a defect?​  

The variance between actual result and expected result is known as a defect. 

What is a bug?   

If testers find any mismatch in the application or system in a testing phase and then that defect is accepted by the developer then it’s called it as Bug. 

What is an error?  

When a developer can’t compile or run a program due to a coding mistake in a program.
 i.e. if programmer unable to successfully compile or run a program then they call it as an error. 

What is a failure?    

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

What is a fault?  

Faults are the result of an error. ​ ​It is a condition in which the software fails to perform its required function ​i.e. the incorrect step or process due to which the program or the software behaves in an unexpected manner.

Comments

  1. Unknown21 June 2019 at 20:12

    Very nice site for software testing learning in detail.... Thanks bhushan

    ReplyDelete
  2. Dhanashree1422 June 2019 at 05:23

    i used to be always confused in these 4... thnx for simplifying it....

    ReplyDelete

Post a Comment

Popular posts from this blog

Implicit and Explicit requirements

-
Implicit and Explicit requirements Explicit Requirements​ :    ● The Things business analyst Wrote Down.  ● These are the requirements explicitly stated or mentioned by the customer.  ● Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.   ● This is the simplest type and the easiest to test.  ● The development team might take the form of an elaborate design specification, a set of acceptance criteria.  ● Explicit requirements in the form of claims that is, communications to end-users about things the software can do.   Implicit Requirements​ :  ● The Things client Will Expect  ● These are the requirements that are not explicitly stated by the customer, but implied or derived from the requirement stated by the customer.  ● These are all the things that users are going to expect that were not captured explicitly.  ● Examples include performance...
Read more

Software Configuration Management (SCM)

-
Software configuration management (SC) is a software engineering discipline consisting of standard processes and techniques often used by organizations to manage the changes introduced to its software products. SC helps in identifying individual elements and configurations tracing changes and version selection control and baselining.   SC is also known as software control management. SC aims to control changes introduced to large complex software systems through reliable version selection and version control.   Software Configuration Management does​ ​   ● Introduction to Software Configuration management and Configuration management for software Testers.  ● Software configuration management (SC) is the discipline for systematically controlling the changes that tae place during Software evelopment.  ● Software development software consists of a collection of items (such as program documents etc..) that can easily be changed. uring software...
Read more

Identified for Configuration Management

-
The term configuration item (CI) refers to the fundamental structural unit of a configuration management system. Examples of CIs include individual requirements documents software models and plans. The configuration-management system oversees the life of the CIs through a combination of processes and tools by implementing and enabling the fundamental elements of identification change management status accounting and audits. This system aims to avoid the introduction of errors related to lack of testing as well as incompatibilities with other CIs.     Configuration Management Activities ​:     1. ​Configuration Item Identification ​:  ​In this phase, the item will be identified for making changes.  Example: ​Requirement document design document source code etc    2. ​Change Control ​: ​ Controlling the release and changes of the product throw out the software life cycle here CCB team will approve or disapprove changes prioritize the change...
Read more