PowerPoint Presentation

- By Pradeep Pawar

ContentsWhat is a BUG?

First Software Bug

Bug fixing cost

Reasons why bugs get into software

Bug life cycle

Life Cycle Stages

#

2

ATSWhat is a BUG?3Abnormal 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, but the code fails to correctly conform to this behavior because of incorrect implementation in coding

#

3

ATSEver wondered where the term bug came from?4In September 9, 1945, U.S. Navy officerGrace Hopper found a moth between the relays on the Harvard Mark II computer she was working on.

The term bugs in a computer had been used before, but afterGrace Hopper wrote in her diaryfirst actual case of bug being found the term became really popular, and thats why we are still using it today.

#

4

ATSBug fixing cost

5Later a bug is found The more it costs.

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, resource effort hours etc. 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.

#

5

ATSReasons why bugs get into software

6Human factor:Human beings develop software. Different level of understanding/intelligence.

Communication failure:different levels (requirement gathering stage, requirement interpretation/documentation stage, requirement-to-implementation translation stage etc.)Example: problem with communication may arise when a programmer tries to modify code developed by another programmer. 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. owner.

Unrealistic development timeframe:crazy release schedules, limited/insufficient resources unrealistic project deadlines.

Poor design logic:Lack of patience and an urge to complete quickly Easiest way to implement solution, lack of proper understanding of the technical feasibility

Poor coding practices:Inefficient or missing error/exception handling, Lack of proper validations (datatypes, field ranges, boundary conditions, memory overflows etc.)

#

6

ATSReasons why bugs get into software

7Lack of version control:Encountering lots ofregression bugsat regular intervalsExample: 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.

Buggy third-party tools:Bugs in third party tools used for class libraries, shared DLLs, compilers, HTML editors, debuggersExample: Dev express controls having compatibility issues in ER portal

Lack of skilled testing:Shortcomings in the testing process that are followed. Lack of seriousness for testing Scarcity of skilled testing resources

#

7

ATSBug life cycle8Journey, which a defect goes through during its lifetime.

Should go through the life cycle to be closed.

Attains different states in the life cycle.

#

8

ATSLife Cycle Stages

9New -Potential defect that is raised and yet to be validated.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 -Assigned against a development team to address it but not yet resolved.Example: The issue details are explained to dev. Owner for Jobs Approval page and added to HM portal buglist against the owners name

Active -The Defect is being addressed by the developer and investigation is under progress. At this stage there are two possible outcomes; viz - Deferred or Rejected.Example: The issue is then being reproduced, debugged and fixed by Dev. Owner.

Test -The Defect is fixed and ready for testing.Example: The fix is handed over in the form HM portal build release to QA team to test the fixed bug.

#

9

ATSLife Cycle Stages

10Verified -The Defect that is retested and the test has been verified by QA. Example: QA team test the issue in the current HM portal release.

Closed -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: If issue is not getting replicated then QA team marks the test case PASS and closes the raised bug.

Reopened -When the defect is NOT fixed, QA reopens/reactivates the defect. Example: If issue is getting replicated in the current build then QA team marks the test case FAIL and reopens the raised bug.

Deferred -When a defect cannot be addressed in that particular cycle it is deferred to future release. Example: Issues related to Interview and Screening pipeline page in HM portal

Rejected -A defect can be rejected for any of the 3 reasons; viz - duplicate defect, NOT a Defect, Non Reproducible.

#

10

Thank You!!!

Any Questions ?

#

11