Defect Management Click screen to begin

1. Defect Management Click screen to begin

2. Welcome To Defect Management Training Objective: The objective of this course is to learn about standards that emphasize a best practice approach for Defect Management in Quality Center for QA Professionals. This allows for improved test quality and enhanced task management and progress reporting capabilities. This course outline assumes that the student has used Quality Center, at least at a beginner level. During this course, you will learn about the following items : • Adding New Defects • Linking and Associating Defects • Updating Defects • Matching Defects • Filtering Defects / Cross Filtering • Closing Defects • Tracking Defects • Defect Reporting

3. Introduction to the Defect Module Detecting and repairing application defects is essential to the development process. Defects may be detected and added to your Quality Center project during all stages of the testing process.The Defect module allows for the creation and management of all defects and requests for enhancements found throughout the testing life cycle.

4. Defects Module Usage Note: The Defects module is not used as a repository for project risks/ issues, nor as a location to log enhancements not associated to the project under test. The Defects module is used to record any project item that requires work to resolve. While often requiring developers to modify code, a defect could also be logged to; • indicate a business analyst clarifying requirements documents, • test leads updating test scripts, • project related situations that require resolution.

5. Recommended Defect Logging Guidelines TIP: If a defect is found and there is not a corresponding test to associate with the defect, consider creating a new test to associate with the defect. When you log a new defect, consider the following recommended Defect Logging Guidelines: • A defect should ALWAYS be opened when a test case is failed (in the Test Lab). • Associating a failed test case with a defect provides assurance that the new and existing software is being effectively tested. It also ensures that the tests created are being properly tracked and managed. • Always include the following information in the description field: • Test Name • Run Step • Description • Expected Result • Actual Result

6. TIP: Enter one defect per Quality Center defect record. This makes defect resolution and tracking easier. Recommended Defect Logging Guidelines – continued When creating a defect, ensure that you provide as much detail as possible to re-create the defect. Items can include: • The System IDs or Roles that were used during the test. • What time of day did the defect occur? • This is important because time stamping the issue could be traced back to an environment problem, such as a new version of software being deployed at the time the defect was encountered. • If you can recreate the defect, what are the steps you took to reproduce? • System logs, which can contain valuable troubleshooting information. • Error messages. • The type of error that was displayed when the defect occurred. • Actual test results. • Comments. • Include comments via the Add Comments button when progress, status, or additional communication is needed between interested parties handling the defect.

7. Recommended Defect Logging Guidelines - continued • Agreeing on priority and severity of defects. • Setting and tracking target resolution date of defects. • Agreeing on status of defects. • Assessing impact to test schedule and recommend remedial action as required. • Approving migration of defect fixes. • Deciding whether to recommend suspension of testing if the system under test is highly unstable. Form a Defect Review Group • Be sure to form a Defect Review Group for the project to be tested. The Defects that are added during the testing phase, may affect multiple systems and timelines. This will require a formal and disciplined approach in the defect resolution. The group’s responsibilities would include:

8. Adding New Defects

9. Introduction to Adding New Defects • Important steps to follow. • Fields that are required when adding a new defect. • How to set the correct Priority and Severity. • How to apply the proper fields such as: • Status • Defect Type • Root cause Now, let’s look at what is involved when Adding New Defects. In this section, you will learn: 9

10. Adding New Defects You use the Defects Module in Quality Center to add defects for your application directly to a Quality Center project. You can then track defects until they are resolved. To add a new defect: Click New Defect from the Quality Center Home Page. After clicking the New Defect button, the New Defect window opens. In the Description field, the tester entering the defect should include the test steps they executed in creating the defect so that it can be recreated by the applicable test or development team.

11. Adding New Defects - continued • When adding a new defect, here are some important steps to follow: • Log defects for any significant deviation from requirements or test cases that did not meet expected results (failed tests). • Ensure that for any failed test case, there is a defect that can be associated with it. Whenever possible: • Log the defect from the failed test case in the test set to establish a link between the defect and the test case (instead of logging defects independently). • Include steps to recreate the error. • Avoid including account numbers and other sensitive customer information in the defect description. Be sure to have a separate attachment with the loan numbers, etc.

12. Adding New Defects – Field Definitions TIP: It is recommended that the test lead identify and communicate which values the project team members should select when logging defects, to ensure data integrity on the defect record. Defect submitters should either type the values into the field or drill down to select values from the list. Several Enterprise Standard fields are utilized at different stages of a defect's life cycle. Let's take a closer look at the fields utilized for a new defect. These fields are: Note: The Finding Group and Owning Group fields utilize the same list of values. Summary - A short description of the defect, which will be used as the Defect Title. Application - The primary application the defect impacts. Detected In Cycle - Testing cycle in which the defect was detected. . Assigned To - The name of the person assigned to analyze, fix, or test the defect. . Detected By - Tester who detected the defect. Project -The name associated with a development effort. Finding Group - The group that finds or discovers the defect. Detected on Date - Date defect was detected (system generated with current date, can be adjusted). Owning Group (Not Shown)- The business or application group which owns the resolution of the defect. (The group responsible for the fix.). This value should never change.

13. Adding New Defects - Priority vs. Severity TIP: Defect Severity and Priority should be used in conjunction with each other. As part of adding a new defect, two important fields are Priority and Severity. These fields are used to help make management decisions on defect resolution. Priority is assigned to a defect to indicate the business impact and how quickly the defect needs to be resolved. Examples: • Hi Priority, Low Severity defect – Incorrect Company logo may be a quick project fix, but would be major business impact if implemented. • Low Priority, Hi Severity defect – This may be a Defect in a function used by a few application users (so relatively low business impact), but is blocking execution of large portion of test scripts and puts completion of test phase at risk.

14. Adding New Defects - Priority Required Field 1-Urgent – This defect would have a major impact on business operations. There is no possible patch/workaround process. This must be fixed immediately. 2-High – This defect would have a major impact on business operations. The problem should be fixed before release of the current version in development, or a patch/workaround process would be needed prior to implementation. 3-Medium –This defect would have moderate impact on business operations. The problem should be fixed before release of the current version in development, or a patch/workaround process would be needed prior to implementation. 4-Low –This defect would have a minor impact on the customer. The flaw should be fixed if there is time, but it can be deferred until a later date determined by business need. Priority is the evaluation of the significance of a defect from the business perspective. It defines the precedence for fixing and re-testing of the defect. The different Enterprise Standard values are:

15. Adding New Defects - Severity Required Fields Urgent - A major problem, which has halted the test cycle and requires immediate response. Must be fixed before go-live High - Major problem, which may have immediate or very high potential for significant impact to the test cycle. Must be fixed before go-live. Medium - An issue that imposes some loss of functionality, but for which there is a workaround that would allow testing to continue. The defect has the potential of impacting the test cycle. Testing can proceed without interruption. Does not need to be fixed before go-live. Signoff (to proceed with as a known issue) will be required before go-live. Low - A minor issue that imposes some loss of functionality, but for which there is an acceptable and easily reproducible workaround. Testing can proceed without interruption. Does not need to be fixed before go-live. Signoff will be required before go-live. Severity is the combined technical team’s best evaluation of the criticality and complexity of the change and its potential impact on the timely completion of the overall project. The different Enterprise Standard values are:

16. Adding New Defects – Status Field New – Status is set to New when the problem is first reported. Open – Status is changed to Open after the Project Team has accepted the defect. At this point it is ready to be assigned to a developer/ BA/ business team. Assigned– Owner is actively working on resolution of the defect. Fixed – Status is changed to Fixed after the developer has a resolution for the defect, executed the fix, unit tested the fix, and it is ready for review and packaging to the test environment. Defect should also remain in this status until the developer retests it in the test environment. Ready for Re-test – When the code fix has been packaged and released by development to the testing environment to be tested by the originator of the defect. Re-Opened – Status is changed to Re-Opened, if the actual results of the test still do not match expected results after being fixed. Now we will look at the Status Field. It is a required field. This field specifies the current stage of the defect. This field defaults to “New”, when a defect is added to Quality Center. The Status values that specify a defect needs work to resolve are:

17. Adding New Defects – Status Field The Status Field also allows you to assign an end state status. The end state status is used to classify the defect as no longer needing work to resolve. The end state values are: Closed – Status is changed to Closed when the necessary parties agree that the defect resolution meets requirements and the actual results match the expected results. This is an end state in the defect workflow. Deferred – The defect will not be closed until a later build or release. It is currently being held as a known defect. Duplicate - The defect is a duplicate of another previously identified defect and should not be counted against overall defect counts. This is an end state of the defect workflow. Rejected – A defect is rejected if: The defect cannot be reproduced; The deliverable under review is correct; it was an error in the test expectations or execution. 17

18. This is the Enterprise Standard Defect and Process Workflow. It shows the lifecycle of the defect, the status workflow and the responsibilities of the finding and owning groups. It is a good reference point for you to follow when opening, tracking, retesting, and closing defects. The flowchart can be found on the Quality Practices Library website at http:\\qpl.bankone.net Adding New Defects – Status and Process Flow

19. Adding New Defects - Defect Type and Root Cause fields Defect Types Root Cause The next two fields are the Defect Type and Root Cause fields. These fields become populatedonce a defect is assigned and the status is changed to Fixed. • The Defect Type is a defect classification to assist in resolution assignment. • The Root Cause is the origin of the defect/problem/issue. The table below shows the Defect Type and the corresponding Root Cause. 19

20. Adding New Defects - Defect Type and Root Cause fields - continued As you select the different Defect types, you are presented with various combinations of Root Cause. This is because the Root Causedropdown list is automatically populated based on the selected Defect Type. Defect Types Root Cause 20

21. Linking and Matching Defects

22. Introduction to Linking Defects • This section covers Linking and Matching Defects. Defect linkage is useful, for example, when a new test is created specifically for a defect. By creating this linkage, you can determine if the test should be run based on the status of the defect. • You can link a defect to the following entities: • Requirements • Tests • Test sets • Test instances • Runs • Run steps • Other defects • A defect can be linked directly or indirectly to an entity. When you add a defect link to an entity, Quality Center adds a direct link to this entity and indirect links to other related entities. In addition, during a manual test run, if you add a defect, Quality Center automatically creates a linkage between the test run and the new defect. • You can add a defect link by submitting a new defect or by selecting an existing defect. When you link an entity to a defect, Quality Center adds the icon to the entity and to the linked defect.

23. Linking Defects Click this icon to view linked entities for the defect. To set column appearance and order in the grid, click the Select Columns button. To view details of a defect, select a defect link and click the Defect Details button. The Defect Details dialog box opens. To open a linked defect in the Linked Entities menu, click the Go To arrow and choose Go To Defect. Alternatively, click the Defect ID link to open the linked defect. Now, let’s look at the Linking functionality within Quality Center. Below are some of the buttons you will be using toLink Defects. 23

24. Linking Defects When the Defects Tab is clicked within the Linked Entity Defect Details window, the Grid displays the Defect Summary, Linked Entity, and Linked Comment. From this screen, the grid has many customizable choices to display the columns. When the Others Tab is clicked within the Linked Entity Defect Details window, the Grid displays all available columns by default. Other areas you will utilize are the Defects Tab and the Others Tab in the Defect Details Window. See below for a description of each. 24

25. Linking Defects - Adding Links by Selecting the Defect ID In the Linked Defects tab or dialog box, click the Link Existing Defect arrow, or right-click the grid and choose Link Existing Defect. Choose By ID or Select: To add a link by typing a defect ID, choose By ID. In the Link Existing Defect dialog box, type the defect ID and click Link. The defect link is displayed in the grid. To add a link by a selecting a defect, choose Select. In the Defects to Link dialog box, select the defect. To select more than one defect, press the CTRL key and select the defects you want to link. Click Link. The defect links are displayed in the grid. You can add a defect link by specifying an existing defect ID. To add a link by specifying an existing defect:

26. Matching Defects NOTE: Note that keywords are more than two characters, and letter case does not affect your results. The following are ignored: articles (a, an, the); coordinate conjunctions (and, but, for, nor, or); boolean operators (and, or, not, if, then); and wildcards (?, *, [ ]). Matching defects enables you to find and eliminate duplicate or similar defects in your project. Each time you add a new defect, Quality Center stores lists of keywords from the Summary and Description fields. When you search for similar defects, keywords in these fields are matched against other defects. There are two methods you can use to conduct a search for similar defects: • Find Similar Defects. Compares a selected defect with all other existing defects in your project. You can conduct a search for similar defects in the Defects Grid, or before submitting a new defect in the new Defect dialog box. • Find Similar Text. Compares a specific text string against all other existing defects in your project. You can conduct a search for similar defects in the Defects Grid, or before submitting a new defect in the new Defect dialog box. You can limit your results by specifying a percentage of detected similarity.

27. Matching Defects - Finding similar text strings within defects. You can match defects by comparing a specific text string with all other existing defects in your project. You can limit the results of defects found to those that meet a specific similarity percentage. For example, suppose that you are searching for defects with the word Help. If you limit your results to 25 percent, the search returns the following results: If you limit your results to 100 percent, the search returns the following results:

28. Matching Defect - How To find similar text: • In the Defects Grid, click the Find Similar Defects arrow and choose Find Similar Text. Alternatively, in the new Defect dialog box, before you submit a defect, click the Find Similar Defects arrow and choose Find Similar Text. The Find Similar Text dialog box opens. • To limit the results of defects found to those with a minimum similarity, type a percentage in the Percent of Similarity box. By default, Quality Center returns defects with a similarity of at least 25 percent. • In the Text to Find box, type the text string. • Click OK. Results are displayed in the Similar Defects dialog box, ordered by percentage of detected similarity, as listed in the Similar column. If no similar defects are found, a message is displayed. • To see more details for a defect in the Similar Defects dialog box, double-click the defect. • Click Close to close the Similar Defects dialog box.

29. Filtering Defects

30. Filtering Defects TIP: You can save filter and sort information as a favorite view and then load it as needed. To save as a favorite view, choose Favorites > Add to Favorites. You may add as many filters as you need to obtain the desired view. This view becomes your default view the next time you log into Quality Center. When filtering defects, the following options are available in Quality Center • Set Filter Conditions • Set View Order • Group Items • Save Filtered Defect List to Favorites • Export Filtered Defects List

31. Filtering Defects – Specifying columns and setting filter conditions Click the Columns button to add more fields in the Defect grid. Choose fields to display in the Select Columns window. If needed, re-arrange the order of the columns. Click the Set Filter Sort button to select specific defects. Define the criteria for the query in the Filter window by specifying a condition. You have the ability to customize the Defect Details by adding or removing columns. To Add Columns: Referring to the picture to the left - 31

32. Filtering Defects - Selecting a Filter to View in the Filter Options First, scroll or begin typing to locate the attribute on which you wish to filter, then select the build button to locate the values. Second, click on the values and operators to build a logical filter (highlighting and hitting the enter key will not work). Third, add as many filters as you need to obtain the desired view. This view becomes your default view the next time you log into Quality Center. In Quality Center, you can filter on defects to specify items to display in the defect grid. This filter will become your default view in Quality Center. Setting a Filter is useful when you are searching for a particular attribute. To set a filter condition: Referring to the picture to the left - 32 32

33. Filtering Defects - Filter By Grouping Defects Open the Filter window. In the Filter window, click on the Group tab. Select the attributes you wish to Group Items by. (You can select up to 3 types of attributes to group by) The following Grouping is Displayed. Click the OK button. You can also filter defects by grouping items. Below is the Filter By Group menu which is accessible within the Filter window when the Group tab button is clicked. This menu enables you to group filters by the various items in the menu selections. To Filter Defects by grouping items, follow these steps: . 33

34. Filtering Defects - Adding Filtered Defect List to Favorites. If you need to recall a specific filter in the future, you can save time by saving a filter you created to your Favorites. To save a configured filter to Favorites: • Click on the Favorites option on the menu bar and select Add to Favorites. • Give your Filter a descriptive name in the Add Favorite Dialog box • Click the OK button. • Your Favorite will now be accessible under the Favorites Menu for future sessions. 34

35. Filtering Defects - Exporting Filtered Defects • Once you have your preferred defect list • filtered, you can export that view • using the Quality Center Export Feature. • To use the export feature; • Set your Filter condition. • Click the Defects menu selection. Select EXPORT All or Selected • Name the File to be exported and select the option Save As Type. You can export the results into several formats. • Click the Save button to complete the export. 35

36. Filtering Defects - CROSS FILTERING The Defect Module also has an advanced second filtering option. Cross Filtering allows you to narrow your search on an item. Use a cross filter to ensure specific information is displayed. Defect Module Cross Filter options: • Requirements – Filter the Defect by linked requirements. • Test Sets – Filter the defects by linked test sets. • Test – Filter the defects by linked test • Show Defects With Alerts – Filter the defects by alerts that have been triggered.

37. Closing Defects

38. Closing Defects - Required Fields When Closing a Defect Closed - The defect status is changed to Closed when the necessary parties agree that the defect resolution meets requirements and the actual results match the expected results. This is an end state in the defect workflow. Closed in Level – The testing level where the defect was actually closed. When the Defect Status is equal to “Closed”, this field is automatically populated with the Testing Level associated with the Target Cycle field. The user has the option to edit this field.

39. Closing Defects - Target Cycle and Planned Closing Date Planned Closing Date –The date on which the defect status will become closed. This field defaults to the Cycle End Date when the Defect Status is equal to “Ready for Re-Test” but can be modified. Target Cycle - Indicates in which cycle the defect is targeted to be closed. When the defect status is equal to “Closed” the Target Cycle is considered the cycle in which the defect was closed (Closed in Cycle).

40. Defect Reporting and Graphs

41. Tracking Defects Expand All to view a list of fields modified during the change. For each field, the grid displays the old value and the new value. To expand all changes, click the Expand All button. First, double-click a defect to open the Defect Details dialog box. Once open, click History on the sidebar. The history of changes made to the defect is displayed in a grid. For each change to the defect, the grid displays the date and time of the change and the name of the user who made the change. You can specify which changes are displayed in the grid. In the Field list, select a field name to view only changes made to that field. Select <All> to view changes made to all fields. Viewing Defect History Reporting and metrics of defects are an important part of the project being tested. In Quality Center, you can generate these reports and metrics. Before we look at generating reports and graphs in Quality Center, let’s look at tracking defects. In Quality Center changes to the status, priority, severity, and many other fields are saved to the Defect History. This log of changes is useful when you need to view who changed a value in one of the fields or when a value was changed. To view the history of changes to a defect:

42. Generating Reports TIP: You can save the settings of your reports as favorite views and reload them as needed. You can also export grid data as a text file, Microsoft Excel spreadsheet, Microsoft Word document, or HTML document. Quality Center reports help you assess the progress of defining requirements and tests coverage, the test plan, test runs, and defect tracking. You use reports to assist in determining testing priorities and defect repair schedules, and in setting application release dates. You can generate reports at any time during the testing process. • To access reports, Click on the Defects Module, Select Analysis > Reports > Standard Defect Reports.

43. Defect Standard Reports

44. Creating Customized Reports • Select the Quality Center module from which you want to generate a report. • Choose Analysis > Reports and select the report you want to customize. The report opens with default data displayed. • Click the Configure Report and Sub-Reports button to customize your report. The Report Configuration page opens with the default options displayed. • In the Reports list, select a main report or a sub-report. The Report Configuration pane displays the available options. • Under Page, you can set the number of items per display page (available for the main report): • To limit the number of items per page, select Limit items per page to and specify the number of items per page. • To display all items in one page, select All items in one page. • Under Template, you can use the Quality Center default report template or your own template. (This option is available for the main report only.) • Under Filter, you can define or clear filters and sorting priorities: • Click the Set Filter/Sort button to filter and sort your data according to criteria you choose. • Click the Clear Filter/Sort button to clear all the filters and sorting priorities. • Under Fields, you can set the fields you want to appear in the report and their order. • Select All Fields (auto-layout) to display all fields in the report. • Select Custom Fields (layout), and click the Select Fields button to choose the fields and set their order.

45. Generating Graphs The following graphs can be generated from the Defects Module within Quality Center: • Summary Graph - Shows a summary of the number of defects in a Quality Center project, or the estimated/actual amount of time taken to fix these defects. • Progress Graph - Shows the accumulation of defects in a Quality Center project, or the estimated/actual amount of time taken to fix these defects, at specific points during a period of time. • Age Graph - Shows the lifetime of defects in a Quality Center project. • Trend Graph - Shows the history of changes to specific defect fields in a Quality Center project, for each time interval displayed.

46. Generating Graphs – Defects Summary Graph The Defects - Summary Graph shows a summary of the number of defects in a Quality Center project, or the estimated/actual amount of time taken to fix these defects. The information is displayed according to the criteria that you specify. You can specify the type of data displayed along the x-axis, the type of data displayed along the y-axis, and the defect information by which Quality Center groups the data.

47. Generating Graphs – Defects Progress Graph Grouped By Status The Defects - Progress Graph shows the accumulation of defects in a Quality Center project, or the estimated/actual amount of time taken to fix these defects, at specific points during a period of time. The information is displayed according to the criteria that you specify. You can specify the time interval displayed along the x-axis, the defect information by which Quality Center groups the data, and the data displayed along the y-axis. You can also specify whether you want to view the number of defects or the change in the number of defects.

48. Generating Graphs – Defects Age Graph The Defects - Age Graph shows the lifetime of defects in a project. The lifetime of a defect begins when it is reported, and ends when it is closed. The information in this graph is displayed according to the criteria that you specify. You can specify the defect information by which Quality Center groups the data, and the data displayed along the y-axis. You can also specify the time interval that you want to use to divide the data, if you want to view graph content in two data columns.

49. Generating Graphs - Defect Trend Graph The Defects - Trend Graph shows the history of changes to specific defect fields in a Quality Center project, for each time interval displayed. You specify the field for which you want to view the number of changes, and the time period for which you want to view data.

50. To customize a summary graph: • Choose a field from the X-Axis list to determine the information displayed along the x-axis of the graph. • Choose a field from the Grouped By list to determine the information by which Quality Center groups data in the graph. • Note that you can group the data by string or list fields only. • Under Data Type, you set the y-axis of the graph: • Select Count to display the total number of items (for example, a count of open defects). • Select Sumof and choose EstimatedFixTime to display the estimated time required for fixing the defects, or Actual Fix Time to display the actual time spent on fixing the defects. (Available only in the Defects module.) • Click the Filter button to open the Filter dialog box and filter the graph content. For more information, see Filtering Records. • Click the Refresh button to apply your changes. The new graph is displayed. Customizing Summary Graphs