Assignment Number: 3 - DEFECT TRACKING

AIM: To Log the new defects in the Test Director and prepare Defect Report. OBJECTIVES:- 1. Students should be able to learn how to log the new defect in the Test Director Tool. 2. Students should be able to learn how to prepare the defect report. THEORY:Defect Tracking To track defects, a defect workflow process has been implemented. Defect workflow training will be conducted for all test engineers. The steps in the defect workflow process are as follows: 1) When a defect is generated initially, the status is set to "New". (Note: How to document the defect, what fields need to be filled in and so on, also need to be specified.) 2) The Tester selects the type of defects: Cosmetic Enhancement Omission 3) The tester then selects the priority of the defect: Critical - fatal error High - require immediate attention Medium - needs to be resolved as soon as possible but not a showstopper Low - cosmetic error d) A designated person (in some companies, the software manager; in other companies, a special board) evaluates the defect and assigns a status and makes modifications of type of defect and/or priority if applicable). The status "Open" is assigned if it is a valid defect. The status "Close" is assigned if it is a duplicate defect or user error. The reason for "closing" the defect needs to be documented. The status "Deferred" is assigned if the defect will be addressed in a later release. The status "Enhancement" is assigned if the defect is an enhancement requirement. e) If the status is determined to be "Open", the software manager (or other designated person) assigns the defect to the responsible person (developer) and sets the status to "Assigned". f) Once the developer is working on the defect, the status can be set to "Work in Progress". g) After the defect has been fixed, the developer documents the fix in the defect tracking tool and sets the status to .fixed,. if it was fixed, or "Duplicate", if the defect is a duplication (specifying the duplicated defect). The status can also be set to "As Designed", if the function executes correctly. At the same time, the developer reassigns the defect to the originator. h) Once a new build is received with the implemented fix, the test engineer retests the fix and other possible affected code. If the defect has been corrected with the fix, the test

engineer sets the status to "Close". If the defect has not been corrected with the fix, the test engineer sets the status to Reopen. Defect correction is the responsibility of system developers; defect detection is the responsibility of the test team. The test leads will manage the testing process, but the defects will fall under the purview of the configuration management group. When a software defect is identified during testing of the application, the tester will notify system developers by entering the defect into the Defect Tracker tool and filling out the applicable information. Introduction to Defect Report: Defect reports are among the most important deliverables to come out of test. They are as important as the test plan and will have more impact on the quality of the product than most other deliverables from test. It is worth the effort to learn how to write effective defect reports. Effective defect reports will: . Reduce the number of defects returned from development . Improve the speed of getting defect fixes . Improve the credibility of test . Enhance teamwork between test and development Following a few simple rules can smooth the way for a much more productive environment. The objective is not to write the perfect defect report, but to write an effective defect report that conveys the proper message, gets the job done, and simplifies the process for everyone. Contents: Defect Remarks Essentials for Effective Defect Remarks Defect Abstracts Who reads our defect reports? Project Manager Executives Development Customer Support Marketing Quality Assurance Any member of the Project Team What may happens to these defects? What if your Manager or Team lead is in a meeting where they are looking at hundreds of defects for possible deferral The Product team cannot make the right decisions about this software error Who reads the description part of the defect report? Development

Project Manager Customer Support Quality Assurance Any member of the Project Team

Definitions: Severity: - it indicate how bad the bugs and reflex is impolite on the product and on the user. Priority: - Indicate how important it is to fix the bugs and when it should be fixed. Severity Description Criteria 1 showstoppe Core dumps, Inability to r install/uninstall the product, Product will not start, Product hangs or Operating System freezes, No workaround is available, Data corruption, Product abnormally terminates 2 High Workaround is available, Function is not working according to specifications, Severe performance degradation, Critical to a customer Incorrect error messages, Incorrect data, Noticeable performance inefficiencies Misspellings, Grammatical errors, Enhancement requests. Cosmetic flaws

Medium

Low

Deciding priority Levels of defects: Priority Description Criteria 1 showstoppe Immediate fix, block further r testing, very visible 2 3 High Medium Must fix before the product is released Should fix if time permits

What we need to write in the defect report What are the conditions and the Failure? Use the Failure info. for your Subject line Steps to reproduce the Software Error Determine the Severity & Priority Include the OS & build number Information on other conditions tested Defect Tracking Monitoring defects from the time of recording until satisfactory resolution has been determined. Defect lifecycle Bug lifecycle/Defect tracking lifecycle/change request lifecycle. Defect Tracking: - Monitoring defect from the time of recording until satisfactory resolution has been determine. Bug / Defect Lifecycle

Steps to follow for Testdirector: You have to follow the earlier steps which are explained in assignment 1c. After that click on RUN TESTS TAB=>Test Set Builder=>add created folder to Selected tests.

Selected tests MyTest=>Click on Manual Tab on right side.

Then Run: MyTest tab will be open=>Click on Start Run=>

Now Execute and update the actual result PASS/FAIL for all STEPs.

Now after executing all steps, if any test gets FAILED Then we can log this as new defect in to the Test Director. Select the Failed test as shown below then Click on BUG icon button [New Defect] to log defect.

Then Click on the Create new defect button. Defect is added as number 20.

Following view can be seen in the Run Tests tab.

Following view can be seen in the Track Defect tab, where the defect is successfully recorded at number 20.

Now after selecting the 20th row click on Report button and from the dropdown list select the Standard option.

Now select Complete Information => Portrait=OK as shown below.

Finally the Defects Standard Report is generated.

By selecting Custom view following Defect Status report can be seen.

By selecting Planning Document view following Defect Status report can be seen.

Conclusion: In this assignment we logged new defects in the Test Director and prepared Defect Report.