DEFECTS
1) Locating and repairing application defects efficiently is essential to the development process. Defects can be detected and added to your Quality Center project by users during all stages of the application management process. Using the Quality Center Defects module, you can report design flaws in your application, and track data derived from defect records.
2) Fields related to release management are not available in the Defects module if you are working with the Starter Edition.
3) The defects tracking workflow consists of the following: Add Defects, Review New Defects, Repair Open Defects, Test New Build, Analyze Defect Data.
4) You can associate the new defect with the cycle and release in which it was detected.
5) You can link the new defect with the test you ran, for future reference. You can also link defects to other Quality Center entities, such as requirements, tests and other defects. You can also view, update, and analyze defects in the project.
6) Review all new defects in the project and decide which ones to fix. This task is usually performed by the project manager. Change the status of a new defect to Open, and assign it to a member of the development team.
7) While reviewing new defects, if duplicate defects appear in the project, change their status to either Closed or Rejected, or delete them from the project.
8) Fix the Open defects. This involves identifying the cause of the defects, and modifying and rebuilding the application. These tasks are performed by application developers. When a defect is repaired, assign it the status Fixed.
9) Run tests on the new build of the application. If a defect does not recur, assign it the status Closed. If a defect is detected again, assign it the status Reopen, and return to the previous stage. This task is usually performed by the quality assurance manager or project manager.
10) View data from defect reports to see how many defects were resolved, and how many still remain open. As you work, you can save settings that are helpful in the defect-tracking process, and reload them as needed.
(Lets read more)
11) Reports and graphs enable you to analyze the progress of defect repairs, and view how long defects have been residing in a project. This helps you determine when the application can be released.
12) To find a specific defect by Defect ID in the Defects Grid, choose Defects > Go To Defect.
13) You can access the Defects menu bar from the Defects module by pressing the shortcut key F9.
14) Send by E-mail. Opens the Send E-mail dialog box, enabling you to send defect email to recipients selected from a list, or to any other email address.
15) Find Similar Defects. Conducts a search for similar defects and, if any are found, displays them in the Similar Defects dialog box. 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.
16) You can match defects by comparing a selected defect with all other existing defects in your project. When similar defects are found, they are displayed according to the percentage of detected similarity.
17) Find Similar Text. Opens the Find Similar Text dialog box, enabling you to search for similar defects by specifying a text string and, if any are found, displays them in the Similar Defects dialog box. 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.
18) Quality Center organizes and displays defect data in a grid. Each line in the Defects Grid displays a separate defect record.
19) Actual Fix Time - Indicates the actual number of days needed to fix the defect. If this field is left blank, Quality Center automatically calculates the Actual Fix Time as Closing Date - Detected on Date.
20) When assigning a defect to a cycle in the Detected in Cycle field, Quality Center automatically assigns its release to the Detected in Release field.
21) The priority of the defect, ranges from low priority (level 1) to urgent priority (level 5).
22) The severity of the defect, ranges from low (level 1) to urgent (level 5).
23) Status - The current status of the defect. By default, the status is New. Defect status can be one of the following: Closed, Fixed, New, Open, Rejected, Reopen.
24) When assigning a defect to a cycle in the Target Cycle field, Quality Center automatically assigns its release to the Target Release field.
25) You can add user-defined fields and change the label of any of the fields in the Defects Grid. You can also customize project lists.
26) You can use the Script Editor to restrict and dynamically change the fields and values in the Defects Grid.
27) We can track defects until the application developers and application testers determine that they are resolved.
28) Defect records inform members of the application development and quality assurance teams of new defects discovered by other members. By sharing defect information, both the application development and defect repair processes are faster, more efficient, and more comprehensive.
29) You can use the Workflow Script Editor to restrict and dynamically change the fields and values in the Defects module. You can also customize the fields for a specific user group.
30) You can share defects across multiple Quality Center projects. You share and synchronize defects using the HP Quality Center Synchronizer.
31) In addition to adding defects directly in Quality Center, you can also import defect data from Microsoft Excel to your Quality Center project.
32) Matching defects enables you to 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.
33) The 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 (?, *, [ ]).
34) If the defect is linked to a test run, you can click the Execution Report link at the bottom of the Defect Details dialog box to generate an execution report. The execution report displays detailed information about the linked test run.
35) You can search and replace field values in the Defects Grid using the Find/Replace command.
36) You can view a list of changes made to a defect. Note that you can only see changes for selected fields predefined by the project administrator in Project Customization.
37) You can send email about a defect to another user. This enables you to inform development and quality assurance personnel about defect repair activity. Quality Center includes a Go To Defect link in the email, which enables the recipient to go directly to the defect.
38) You can automatically send the email to a specific user type. This can be any defect column with a user name value, including user-defined fields. Click the Send by Email arrow and choose an option.
39) You can copy a defect to any Quality Center project. You can copy a defect and paste its URL as a link. The defect itself is not copied. Instead, you can paste the address into another location, such as an email or a document. Clicking on the link opens up Quality Center and takes you to the defect. If you are not already logged in, Quality Center first prompts for login details.
40) You can print all defects or selected defects in the Defects Grid.
41) You can delete old or duplicate defects from a project. When you delete a defect, Quality Center does not reuse the Defect ID.
42) You can link a defect to the following entities: requirements, tests, test sets, test instances, runs, run steps, and other defects.
43) 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.
44) When you link a defect to a run step, Quality Center adds an indirect link to its run, test instance, test set, and test. If the same test is covered by a requirement, an indirect link is also added to the requirement. Note that the indirect linkage is a one-directional flow. For example, if you link a defect to a run it is not indirectly linked to its run steps.
45) Flow of Indirect Linkage - Run Step > Run > Test Instance > Test Set
Test > Requirement
46) To display direct links, from the Type of Link list, select Direct Links. To display direct and indirect links, select All Links. Not available in the Defects module.
47) To display defect links added to parent requirements, select Current Req Links from the Show Links For list. To display defect links added to parent and children requirements, select Including Child’s Links. Available only in the Requirements module.
48) You can remove defect links from the Linked Defects grid. You can only remove direct links. Indirect links are removed automatically when the direct links are removed.
No comments:
Post a Comment