Bug Tracking of power point

Bug Tracking SystemsConfidential2Topic Organization1.Bug & Basic Terminology 2.Evaluation of Bug Tracking System3. Bug Reporting and Tracking-WWWH •What is Bug Reporting and Tracking?•Who are involved in Bug Reporting and Tracking?•Why to Report and Track a Bug?•How To Report and Track a Bug? Bug Life cycle-StepsBug Tracking Systems4. Effective Bug Reporting5. Perfect Bug Tracking Confidential3Topic 1Bug & Basic TerminologyConfidential4Bug & Basic TerminologyError: Deviation for actual and the expected/theoretical value.It refers to the discrepancy between a computed, observed, or measured value and the true, specified, or theoretically correct value. That is, error refers to the difference between the actual output of a software and the correct output. Bug: An Error found in the development environment before the product is shipped to the customer. Defect: An Error found in the product itself after it is shipped to the customer.Failure: A system is said to have a failure if the service it delivers to the user deviates from compliance with the system specification for a specified period of time.Enhancement: An improvement to an existing feature. Feature: An addition to the software to add a piece of functionality that does not yet exist. Patch: A section of code to be applied or attached to existing software, often to fix a defect. Confidential5Topic 2Bug Reporting & TrackingWWWHWhat? Who? Why?How? Confidential6WWWHWhat is Bug Reporting and Tracking?Who are involved in that?Why Bug Reporting and Tracking?How to Track a Bug?Confidential7What is Bug Reporting and Tracking? Bug Reporting :A person who uses a product Reports a Bug/Malfunctioning ..etc to a person who developed the productBug Tracking :Managing and Reviewing a bug and its statusBug Tracking System :This is a system designed especially to manage software problems, enhancement, change request during software development life cycle. Confidential8Who are involved in that?Customer/Reporter:The Customer role is the person who files the bug report. It may be a real end user customer, or it may be a QA Engineer, or an IT project team member. In all cases, the duties are the same. Programmer:The Programmer is the role taken by the person who is assigned to fix and regression test to make sure the fix didn't break other features in the system. Tester: The role of Tester is to verify the fix and validate it against the bug reported Dispatcher/Review Team:The Dispatcher has the role of setting priorities and assigning bugs to be worked on, then following up on work. The Dispatcher can coordinate the life cycle events between various other roles. The Dispatcher can be a Systems Analyst, Developer, etc.Confidential9Why Bug Reporting and Tracking?Why Bug Reporting?•Malfunctioning of the application•Missing Functionalities •To enhance the existing features of an application (Change request)•To add the extra features to an applicationConfidential10Why Bug Reporting and Tracking?Why Bug Tracking?•Milestones -Triage Process•Severity•Priority Confidential11Milestone -Triage Process Milestones -Milestones are planned events when certain planned deliverables are provided. These are achievable short term Targets at which it is possible to evaluate progress towards a final Objective. Each output of one milestone is marked as input to next milestone.Triage Process -This is the process by which “new” defects are reviewed and action taken.A “new” defect will be reviewed by the “Review Team”The “Review Team” can take a number of actions that result in changes to either the STATUS and/or the Assigned-To field.1.Defer: If the bug is a valid bug but it won’t be fixed in the near future 2.Assign: If the bug is something that needs attention then the Assigned-To field will be set to a named person. 3.Close: If the “Review Team” decide the bug is not a bug Confidential12Severity This field describes the impact of a bug. The submitter of the bug should consider carefully their view of the bug severity, i.e. the impact to them as the end user.BlockerBlocks development and/or testing work Criticalcrashes, loss of data, severe memory leakMajormajor loss of function NormalMinor loss of function.Unfriendly behavior that is hindering, but workable, for the user or serviceMinorMinor loss of function.Unfriendly behavior that is merely annoying to the userTrivialcosmetic problem like misspelled words or misaligned text EnhancementRequest for enhancementNote: The default severity is Normal.Confidential13PriorityPriority is used to organize the work.This field describes the importance and order in which a bug should be fixed. The field only takes meaning when owner of the bug P1Fix in next buildP2Fix as soon as possibleP3Fix before next releaseP4Fix if time allowsP5Unlikely to be fixedDefault priority for new defects is set at P3.Confidential14Bug States/Life CycleBug Tracking SystemsHow to Track a Bug?Confidential15Bug Life Cycle-Steps As defects move through the system they are given various states. At each state there are a number of possible transitions to other states Confidential16Bug Life Cycle-Steps NEWRecently addedto ASSIGNED by acceptanceto RESOLVED by analysis and maybe fixingto NEW by reassignmentASSIGNEDThe owner, i.e. the person referenced by Assigned-To has accepted this bug as something they need to work onto NEW by reassignmentto RESOLVED by analysis and maybe fixingREOPENEDWas once resolved but has been reopenedto NEW by reassignmentto ASSIGNED by acceptanceto RESOLVED by analysis and maybe fixingNEW ASSIGNED RESOLVED VERIFIED CLOSEDREOPENEDConfidential17Bug Life Cycle-Steps RESOLVEDHas been resolved (e.g. fixed, deemed unfixable, etc. See "resolution" column)to REOPENED by reopeningto VERIFIED by verificationto CLOSED by closingVERIFIEDThe resolution has been approved by QAto CLOSED when the product shipsto REOPENED by reopeningCLOSEDOver and done withto REOPENED by reopeningNEW ASSIGNED RESOLVED VERIFIED CLOSEDREOPENEDConfidential18Bug Life Cycle-Resolutions ResolutionMeaningFIXEDThe bug has been fixed.INVALIDThe problem described is not a bug.WONTFIXThis bug will never be fixed.LATERThis bug will not be fixed in this version.REMINDThis bug probably won't be fixed in this version.DUPLICATEThis is a duplicate of an existing bugWORKSFORMEThis bug could not be reproduced.MOVEDThis bug has been moved to another database.Confidential19Bug Life Cycle-Resolutions NewAnalysis -Prod MgmtAnalysis -QA Analysis -DevReviewTargetedDevelopmentCode CompleteDeployedQARejected by TestVerifiedUATAcceptedReturned to SubmitterDeferredClosedNew FeatureChange RequestProblem ReportTaskCurrently UnresolvedCannot ReproduceNot NeededWork to CompletionWorks as DesignedStatusTypeResolutionGemini NomenclatureConfidential20Better Approach Confidential21Bug Tracking Systems (tools)Web BasedClient-Server BasedBug Trackers Integrated with version control Confidential22Topic 3Effective Bug Reporting Confidential23Effective Bug Reporting Keep bug reporting simple: Don't make bug reporting complicated by requiring entry of more data than is really necessary Describe how to reproduce bugs:A bug report should include a step-by-step description on how to reproduce the bug (or replication information)Record how bugs are detected:Report all the facts-Allow them to reproduce the bugWrite bug reports immediately :the longer you wait between finding the problem and reporting it, the more likely it is the description will be incomplete, the problem not reproducible, or simply forgotten.Writing a one-line report summary :Writing theBug's report title is an art. You must master it (the same should be related to bug you are reporting)Don't use the same summary: For two different reports, even if they are similar don’t use similar summaryConsult your peer member: Before writing a bug consult your peer team member (if the same has already been reported).Confidential24The Perfect Bug tracking •Make abuild of the software daily•Use a process to handle bug reports•Resolution field•Handle feature requests separately Confidential25QuestionsConfidential26Thanks You