- By Pradeep


Contents  What is a BUG?  First Software Bug  Bug fixing cost  Reasons why bugs get into software  Bug life cycle  Life Cycle Stages 2 .

but the code fails to correctly conform to this behavior because of incorrect implementation in coding ATS 3 3 .What is a BUG? • Abnormal behavior of the software. • When the expected and actual behavior is not matching • Bug is a specific concern about the quality of the Application • programmer intended to implement a certain behavior.

ATS 4 4 . U.Ever wondered where the term ‘bug’ came from? • In September 9. but after Grace Hopper wrote in her diary “first actual case of bug being found” the term became really popular. • The term ‘bugs in a computer’ had been used before. 1945. and that’s why we are still using it today. Navy officer Grace Hopper found a moth between the relays on the Harvard Mark II computer she was working on.S.

• Example: The approval path in HM portal was not working. This major bug was detected on the verge of release which resulted in additional amount of delivery time. which could have been avoided if the defect was found at unit testing level or regression testing level resulting in timely delivery and savings in resource effort hours.Bug fixing cost • Later a bug is found – The more it costs. ATS 5 5 . resource effort hours etc.

memory overflows etc. • Unrealistic development timeframe:  crazy release schedules.  limited/insufficient resources  unrealistic project deadlines.)  Example: problem with communication may arise when a programmer tries to modify code developed by another programmer. ATS • Poor design logic:  Lack of patience and an urge to complete quickly  Easiest way to implement solution. requirement-to-implementation translation stage etc. owner. Dev Owner of Job pipeline page in HM portal working on bug fix related to Schedules form (which he/she is unaware of) in absence of actual dev.) 6 6 . • Communication failure:  different levels (requirement gathering stage. field ranges. boundary conditions. lack of proper understanding of the technical feasibility • Poor coding practices:  Inefficient or missing error/exception handling. requirement interpretation/documentation stage.  Different level of understanding/intelligence.Reasons why bugs get into software • Human factor:  Human beings develop software.  Lack of proper validations (datatypes.

HTML editors. compilers.Reasons why bugs get into software • Lack of version control:  Encountering lots of regression bugs at regular intervals  Example: Approval path in HM portal working in one build and not working in another build even if not bugs are fixed on the concerned form. debuggers  Example: Dev express controls having compatibility issues in ER portal • Lack of skilled testing:  Shortcomings in the testing process that are followed. • Buggy third-party tools:  Bugs in third party tools used for class libraries. shared DLLs.  Lack of seriousness for testing  Scarcity of skilled testing resources ATS 7 7 .

• Attains different states in the life cycle. which a defect goes through during its lifetime. ATS 8 8 . • Should go through the life cycle to be closed.Bug life cycle • Journey.

Assigned against a development team to address it but not yet resolved.Deferred or Rejected. debugged and fixed by Dev. Example: The fix is handed over in the form HM portal build release to QA team to test the fixed bug. Owner.Potential defect that is raised and yet to be validated. At this stage there are two possible outcomes. Owner for Jobs Approval page and added to HM portal buglist against the owner’s name • Active . Example: The issue details are explained to dev. Example: The search filter values in HM portal displayed in the drop down does not match with the status in the grid which confuses the user • Assigned . viz .The Defect is being addressed by the developer and investigation is under progress. 9 9 .The Defect is fixed and ready for testing.Life Cycle Stages • New . ATS • Test . Example: The issue is then being reproduced.

Life Cycle Stages • Verified .The Defect that is retested and the test has been verified by QA. • Reopened . Example: If issue is getting replicated in the current build then QA team marks the test case FAIL and reopens the raised bug. viz . ATS 10 10 .duplicate defect. • Deferred .When the defect is NOT fixed.The final state of the defect that can be closed after the QA retesting or can be closed if the defect is duplicate or considered as NOT a defect. Example: Issues related to Interview and Screening pipeline page in HM portal • Rejected . QA reopens/reactivates the defect. Example: If issue is not getting replicated then QA team marks the test case PASS and closes the raised bug. Example: QA team test the issue in the current HM portal release. Non Reproducible. • Closed .A defect can be rejected for any of the 3 reasons.When a defect cannot be addressed in that particular cycle it is deferred to future release. NOT a Defect.

Thank You!!! Any Questions ? 11 .