Purge Run is used to delete old test run result in project. By default Purge Run delete all the run result in the selected test sets. Purge run can be used to:
Host manager helps to run test on a host connected to our network. It shows the list of available host for test execution and also organizes them into groups for a specific project.
We can find duplicate bugs in the defect manager tab using “Find Similar Defects” button. We need to enter defect description in brief and it shows similar defects.
Assessment requirement represents requirements that are children of analysis requirement and at lower level in tree hierarchy.
Quality Center is upgraded version of Test Director built by the same vendor Mercury (Now acquired by HP).Test Director Version 8.2 onwards is know as Quality Center. Quality Center is has enhanced Security/Test management /Defect management features when compared to Test Director.
They saved automatically when the users clicks on “END RUN” in the Test Lab.
Version Control helps us to keep track of changes made to entities in our project including requirements. In this we can create and manage QC entities while maintaining previous version of those entities in requirements. To make changes in an entity in a version control enabled project, first we have to check out the entity. When we check out an entity, QC locks the entity, preventing other users from overwriting any changes we make. The checked out version of the entity is not visible to the other user.
We can check out an entity in the following ways:
We determine the risk category for each assessment requirement under the analysis requirement, It has two factors:
1.Install and Configure the Microsoft Excel / Word Add-In for Quality Center.
2.Map the Columns in Word / Excel spreadsheet with Columns available in Quality Center.
3.Export the data from Word/Excel to Quality Center Using Tools >Export to Quality Center Option in Word/Excel.
4.Rectify errors if Any.
Yes we can convert and also generate test case from the requirements. There are two methods we can use to generate tests from the requirements:
We need to specify the users and the privileges for each user.
When we delete a folder or test from the test plan tree there are two ways. We can delete only folder or we can delete that folder, its sub folder and test also. When we delete only folder, all the tests under it moved to the unattached folder in the test plan tree.
Defects can be linked to test in the defect grid. It helps to run the tests based on the status of the defect. Defects can be linked to other entities as well such as requirements. Linking can be direct or indirect. If the defect link is with entity then QC adds a direct link and if the link is with run step then QC adds an indirect link to its run, test instance, test set and test.
The Defect ID is automatically generated after clicking Submit button.
Quality Center is simple and one of the best test management tool. Its benefits are:
A table is a part of database which stores records of information about the test plan.
There are 5 phases:
To see the records that meet the specific criteria that we define we use filters. We can define multiple items as Filter.
The Quality Center modules are:
There are two types of requirements can be added to test cases in Quality Center:
No, we don’t have programming interface in Quality Center.
Defect Tracking means locating and repairing application defect efficiently. Defects can be added or detected to project by the users during all stages of application management process. The defect tracking workflow consists of following:
There are six tables accessible to user via QC’s customized project interface:
To run reports from QC:
Features of QC are listed below:
Test lab is a functionality of Quality center using which we execute tests. We create test trees and add tests to those trees and placed them under test plan in a project. These tests then
Using QTP add-in in Quality Center we can use QTP as an automation tool.
Following are the steps to use Quality Center in real time project.
SQL Server is the default database in Quality Center.
Quality Center live analyses graph provides a visual overview of all tests within a folder in test plan tree.
In order to execute a Test Case (Developed in the Test Plan Module) either manual or automated it needs to imported into Test Lab Module. In sum, Test Cases are created in Test Plan Module while they are executed in Test Lab Module.
To keep track of changes made to entities in the project we use version control. We can create QC entities and also keep previous version of those entities in requirements to track the changes.
After completing the test cases, we do:
Test instance is required to run the test case in the lab. We can’t directly test case in the lab, instead we need to run test instance of that test case.
We can map the requirements with test cases in QC:
@In the requirements tab select coverage view.
@Select requirement by clicking on parent/child or grandchild.
@On right hand side another window will appear. It has two tabs:
(a) Tests coverage
Test coverage tab will be selected by default or you click on it.
@Click on select tests button a new window will appear on right hand side and you will see a list of all tests. You can select any test case you want to map with your requirements.
Roles & responsibilities of QC Admin are:
Reports and graphs can be generated any time and in each and every phase with QC module during the testing process by using default or customize settings like requirement, test plan, test lab or defect module. We can also get summary and progress reports.
Quality Center 8.0 is the first version and Quality Center or ALM 12.0 is the latest version.
Quality Center is a comprehensive test management tool. It is a web-based tool and supports high level of communication and association among various stakeholders (Business Analyst, Developers , Testers etc. ) , driving a more effective and efficient global application-testing process. Automation Tools like QTP , WinRunner & LoadRunner can be integrated with Quality Center. One can also create reports and graphs for Analysis and Tracking for Test processes.
By Creating Child requirements to the main requirement you can evaluate the sub requirements related to the main requirements. You can link test sets and defects to the sub-requirements. This helps in 100% test coverage and its analysis.
To inform any specific user we use test set notification if case of any failure.
Requirement Traceability defines a relationship between two or more requirements. When analyzing the impact of a change proposed in specific requirements, the traceability links indicate the other requirements in the requirements tree; we can establish traceability between the requirements. Using this tab in the Requirement Details view, you can add traceability link to and from selected requirement. Trace from links indicates requirements that affect a selected requirement.
Trace to links indicates requirements that are affected by a selected requirement. When a requirement change QC alerts the affected requirements this can be seen by all users. QC sends email notification to the authors of the affected requirements.
A Test Case imported from Test Plan module to Test Lab module is called an Instance of that test case. It is possible to have multiple instances of the same Test Case in the Test Lab Module.
We can link a test in our test plan to a specific defect in the Defect Grid. This is useful, for example, when a new test is created specifically for a known defect. By creating a linking, we can determine if the test should be run based on the status of the defect. We can also link the defect to other entities, such as requirements.
A defect can be linked directly or indirectly to an entity. When we add a defect link to an entity, QC adds a direct link to this entity and indirect link to other related entities. When we link a defect to run step, it 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, but indirect linkage is one directional flow.
Not Covered status means all those requirements for which the test cases are not written whereas Not Run status means all those requirements for which test cases are written but are not run.
The interfaces of QC are: