1) The Releases module is available for Quality Center Enterprise Edition and Quality Center Premier Edition.
2) The foundation of the Releases module is the releases tree. This tree enables the modeling of upcoming releases within a hierarchical tree structure.
3) A release represents a group of changes in one or more applications that will be available for distribution at the same time. After defining the release, you define cycles.
4) A cycle is a set of development and quality assurance efforts performed to achieve a common goal based on the release timeline.
5) After defining the releases tree, you define and review the requirements in the Requirements module and assign them to releases and cycles.
6) Requirements describe in detail your application needs.
7) Requirements are used as a basis for the test plan in the Test Plan module. The tests you create during the test plan phase should cover these requirements.
8) After assigning requirements to releases and cycles, you assign each test set folder in the Test Lab module to a cycle.
9) A test set is a group of test instances in a Quality Center project designed to achieve specific test goals.
10) If an application flaw is detected while running a test set, you can submit a defect. Quality Center automatically creates a link between the test run, associated release and cycle, and the new defect.
11) While reviewing and deciding which new defects need to be fixed, they can be assigned to the appropriate target release and cycle.
(Let us read more)
12) A defect can be submitted to a Quality Center project from any module at any stage of the application management process.
13) Following test runs, you can review the test progress to determine how well it meets the release goals. You can also determine how many defects were resolved, and how many still remain open. The results can be analyzed at a release or at a cycle level.
14) You can track the progress of the application management process in real time by analyzing the releases tree and ensuring that it matches the release goals.
15) The Statistics pane displays the requirements and test set folders associated with the release or cycle.
16) Progress tab. Shows a high-level overview of the progress of your release or cycle.
17) Quality tab. Shows the number of defects opened over the course of your release or cycle. It also shows the number of outstanding defects.
18) Deleting a release folder also deletes its releases and cycles. Deleting a release also deletes its cycles.
19) The dates for the cycles must be contained within the dates for the releases.
20) You can add user-defined fields and change the label of any of the fields in the Releases module.
21) You can use the Script Editor to restrict and dynamically change the fields and values in the Releases module.
22) The issuing of application releases is often challenging. It requires aligning your business priorities and quality expectations with your project requirements, tests, and defects. Most applications require testing on multiple hardware platforms, multiple configurations (computers, operating systems, and browsers), and multiple application versions. Managing all aspects of an application release can be time-consuming and difficult.
23) In the Releases module, you can organize and track your upcoming releases by defining a hierarchical releases tree containing releases and cycles.
24) Each release can contain a number of cycles.
25) Both releases and cycles have defined start and end dates. After defining the releases tree, you define requirements in the Requirements module and assign them to releases and cycles.
26) Requirements describe in detail what needs to be tested in your application.
27) To cover your requirements, you create tests in the Test Plan module.
28) Then in the Test Lab module, you create a test set folder to store your test sets.
29) Next, you assign the test set folder to a cycle. You then add test sets to your test set folder.
30) Finally, you complete the test coverage planning by adding tests to each test set.
31) You then run your test sets.
32) If application flaws are detected, you can submit defects, which you assign to a particular release and cycle in the releases tree. This enables all relevant developers and testers to determine what
needs to be fixed and the target date for each fix.
33) In the Requirements module, you decide which requirements need to be covered in each cycle and assign them to the relevant cycles accordingly. In the Test Plan module, you then create tests and associate them with the assigned requirements to create coverage. In the Test Lab module, you create test set folders and assign them to specific cycles.
34) The top pane shows the total and remaining days in the release, total test instances for the release, actual and remaining test instances to run, and more.
35) The bottom pane displays the Coverage Progress graph. The curves displayed in this graph are accumulative, that is, each curve is calculated by accumulating all the release information from the beginning of the release.
36) The Assigned requirements curve indicates the distribution of the assigned requirements within the release's cycles.
37) The Planned coverage curve below the Assigned requirements curve indicates the percentage of requirements that are covered throughout the release.
38) The Executed coverage curve below the Planned coverage curve indicates the percentage of tests that were run as the release progressed.
39) The Passed coverage curve is below the Executed coverage curve. It indicates the test runs in which the most recent status is passed.
40) For each cycle, you can view the number of defects submitted and their severity in the Quality tab.
41) You define a hierarchical framework for your releases by creating a releases tree. You start a releases tree by adding a folder under the Releases root folder.
42) An attachment can be a file, URL, snapshot of your application, an item from the Clipboard, or system information.
43) Requirements assigned to release - Displays the number of requirements associated with the selected release. To view the requirements assigned to the release in the Requirements module, click the link displaying the number of requirements. Alternatively, in the releases tree, right-click the release and choose Show Requirements.
44) Requirements assigned to cycle - Displays the number of requirements associated with the selected cycle. To view the requirements assigned to the cycle in the Requirements module, click the link displaying the number of requirements. Alternatively, in the releases tree, right-click the cycle and choose Show Requirements.
45) Test set folders assigned to cycle - Displays the number of test set folders associated with the selected cycle. To view the test set folders assigned to the cycle in the Test Lab module, click the link displaying the number of test set folders. Alternatively, in the releases tree, right-click the cycle and choose Show Test Set Folders.
46) The Progress tab displays statistics and graphs to provide visual indications of the current progress of your release or cycle. This tab shows information such as elapsed and remaining days, completed and remaining test instances to run, and actual and required execution rate.
47) The Quality tab helps you draw conclusions quickly and see the number of defects submitted over the course of a release or cycle. The defects are categorized by severity in terms of how they impact system operation. The severity level ranges from Low-1 to Urgent-5. You can view the graphs at any stage of the application management process to check the progress of your release.
48) Defect Opening Rate - Displays the number of defects opened over the course of a release. The graph displays defects whose Detected in Release value matches the selected release. The defects are grouped according to their level of Severity. The x-axis displays the number of defects according to their severity on the last day of each cycle.
49) Outstanding Defects - Displays the number of outstanding defects for the selected release. The graph displays defects whose Target Release value matches the selected release or is empty. The defects are grouped according to their level of Severity. The x-axis displays the number of outstanding defects according to their severity on the last day of each cycle. By default, New, Open, and Reopened defects are considered outstanding.
50) You can move a release folder or a release to a different location in the releases tree. Moving a release folder also moves its releases and cycles. Moving a release also moves its cycles. The Releases root folder cannot be moved.
51) You can also move a release folder or a release to a new location in the releases tree by dragging it.
52) You can create a duplicate of a cycle within the same release.
53) To duplicate more than one cycle, press the CTRL key and select the cycles you want to duplicate. You can select only multiple cycles that belong to the same release.
54) You can delete a release folder, release, or cycle. When you delete a folder, the releases and cycles under the folder are also deleted. When you delete a release, the cycles under it are also deleted.
55) Deleting a release folder, release, or cycle, also unassigns the associated requirements, test set folders, and defects.
2) The foundation of the Releases module is the releases tree. This tree enables the modeling of upcoming releases within a hierarchical tree structure.
3) A release represents a group of changes in one or more applications that will be available for distribution at the same time. After defining the release, you define cycles.
4) A cycle is a set of development and quality assurance efforts performed to achieve a common goal based on the release timeline.
5) After defining the releases tree, you define and review the requirements in the Requirements module and assign them to releases and cycles.
6) Requirements describe in detail your application needs.
7) Requirements are used as a basis for the test plan in the Test Plan module. The tests you create during the test plan phase should cover these requirements.
8) After assigning requirements to releases and cycles, you assign each test set folder in the Test Lab module to a cycle.
9) A test set is a group of test instances in a Quality Center project designed to achieve specific test goals.
10) If an application flaw is detected while running a test set, you can submit a defect. Quality Center automatically creates a link between the test run, associated release and cycle, and the new defect.
11) While reviewing and deciding which new defects need to be fixed, they can be assigned to the appropriate target release and cycle.
(Let us read more)
12) A defect can be submitted to a Quality Center project from any module at any stage of the application management process.
13) Following test runs, you can review the test progress to determine how well it meets the release goals. You can also determine how many defects were resolved, and how many still remain open. The results can be analyzed at a release or at a cycle level.
14) You can track the progress of the application management process in real time by analyzing the releases tree and ensuring that it matches the release goals.
15) The Statistics pane displays the requirements and test set folders associated with the release or cycle.
16) Progress tab. Shows a high-level overview of the progress of your release or cycle.
17) Quality tab. Shows the number of defects opened over the course of your release or cycle. It also shows the number of outstanding defects.
18) Deleting a release folder also deletes its releases and cycles. Deleting a release also deletes its cycles.
19) The dates for the cycles must be contained within the dates for the releases.
20) You can add user-defined fields and change the label of any of the fields in the Releases module.
21) You can use the Script Editor to restrict and dynamically change the fields and values in the Releases module.
22) The issuing of application releases is often challenging. It requires aligning your business priorities and quality expectations with your project requirements, tests, and defects. Most applications require testing on multiple hardware platforms, multiple configurations (computers, operating systems, and browsers), and multiple application versions. Managing all aspects of an application release can be time-consuming and difficult.
23) In the Releases module, you can organize and track your upcoming releases by defining a hierarchical releases tree containing releases and cycles.
24) Each release can contain a number of cycles.
25) Both releases and cycles have defined start and end dates. After defining the releases tree, you define requirements in the Requirements module and assign them to releases and cycles.
26) Requirements describe in detail what needs to be tested in your application.
27) To cover your requirements, you create tests in the Test Plan module.
28) Then in the Test Lab module, you create a test set folder to store your test sets.
29) Next, you assign the test set folder to a cycle. You then add test sets to your test set folder.
30) Finally, you complete the test coverage planning by adding tests to each test set.
31) You then run your test sets.
32) If application flaws are detected, you can submit defects, which you assign to a particular release and cycle in the releases tree. This enables all relevant developers and testers to determine what
needs to be fixed and the target date for each fix.
33) In the Requirements module, you decide which requirements need to be covered in each cycle and assign them to the relevant cycles accordingly. In the Test Plan module, you then create tests and associate them with the assigned requirements to create coverage. In the Test Lab module, you create test set folders and assign them to specific cycles.
34) The top pane shows the total and remaining days in the release, total test instances for the release, actual and remaining test instances to run, and more.
35) The bottom pane displays the Coverage Progress graph. The curves displayed in this graph are accumulative, that is, each curve is calculated by accumulating all the release information from the beginning of the release.
36) The Assigned requirements curve indicates the distribution of the assigned requirements within the release's cycles.
37) The Planned coverage curve below the Assigned requirements curve indicates the percentage of requirements that are covered throughout the release.
38) The Executed coverage curve below the Planned coverage curve indicates the percentage of tests that were run as the release progressed.
39) The Passed coverage curve is below the Executed coverage curve. It indicates the test runs in which the most recent status is passed.
40) For each cycle, you can view the number of defects submitted and their severity in the Quality tab.
41) You define a hierarchical framework for your releases by creating a releases tree. You start a releases tree by adding a folder under the Releases root folder.
42) An attachment can be a file, URL, snapshot of your application, an item from the Clipboard, or system information.
43) Requirements assigned to release - Displays the number of requirements associated with the selected release. To view the requirements assigned to the release in the Requirements module, click the link displaying the number of requirements. Alternatively, in the releases tree, right-click the release and choose Show Requirements.
44) Requirements assigned to cycle - Displays the number of requirements associated with the selected cycle. To view the requirements assigned to the cycle in the Requirements module, click the link displaying the number of requirements. Alternatively, in the releases tree, right-click the cycle and choose Show Requirements.
45) Test set folders assigned to cycle - Displays the number of test set folders associated with the selected cycle. To view the test set folders assigned to the cycle in the Test Lab module, click the link displaying the number of test set folders. Alternatively, in the releases tree, right-click the cycle and choose Show Test Set Folders.
46) The Progress tab displays statistics and graphs to provide visual indications of the current progress of your release or cycle. This tab shows information such as elapsed and remaining days, completed and remaining test instances to run, and actual and required execution rate.
47) The Quality tab helps you draw conclusions quickly and see the number of defects submitted over the course of a release or cycle. The defects are categorized by severity in terms of how they impact system operation. The severity level ranges from Low-1 to Urgent-5. You can view the graphs at any stage of the application management process to check the progress of your release.
48) Defect Opening Rate - Displays the number of defects opened over the course of a release. The graph displays defects whose Detected in Release value matches the selected release. The defects are grouped according to their level of Severity. The x-axis displays the number of defects according to their severity on the last day of each cycle.
49) Outstanding Defects - Displays the number of outstanding defects for the selected release. The graph displays defects whose Target Release value matches the selected release or is empty. The defects are grouped according to their level of Severity. The x-axis displays the number of outstanding defects according to their severity on the last day of each cycle. By default, New, Open, and Reopened defects are considered outstanding.
50) You can move a release folder or a release to a different location in the releases tree. Moving a release folder also moves its releases and cycles. Moving a release also moves its cycles. The Releases root folder cannot be moved.
51) You can also move a release folder or a release to a new location in the releases tree by dragging it.
52) You can create a duplicate of a cycle within the same release.
53) To duplicate more than one cycle, press the CTRL key and select the cycles you want to duplicate. You can select only multiple cycles that belong to the same release.
54) You can delete a release folder, release, or cycle. When you delete a folder, the releases and cycles under the folder are also deleted. When you delete a release, the cycles under it are also deleted.
55) Deleting a release folder, release, or cycle, also unassigns the associated requirements, test set folders, and defects.
No comments:
Post a Comment