Explore topic-wise InterviewSolutions in .

Using QTP add-in in Quality CENTER we can use QTP as an AUTOMATION tool.

Using QTP add-in in Quality Center we can use QTP as an automation tool.

Business component is used for Business PROCESS TESTING known as BPT. Business component provide script FREE environment for CREATING tests.

Business component is used for Business Process testing known as BPT. Business component provide script free environment for creating tests.

Percentage of testing covered at a GIVEN TIME is KNOWN as Coverage status. It HELPS in tracking project status.

Percentage of testing covered at a given time is known as Coverage status. It helps in tracking project status.

There are two types of requirements can be ADDED to test cases in Quality Center:

• PARENT Requirements which covers high LEVEL FUNCTIONS of the requirements.
• Child Requirements which covers low level functions of the requirements.

There are two types of requirements can be added to test cases in Quality Center:

Following are the steps to use Quality Center in REAL time project.

• Complete the preparation of test cases.
• Export the test cases into Quality Center and Load them in the test PLAN module.
• Move the test cases from test plan TAB to the test lab module.
• Execute the test cases and CHECK for the results.
• If we got any defects and raise the defects in the defect module.

Following are the steps to use Quality Center in real time project.

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.

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.

To run reports from QC:

• OPEN the Quality CENTER project
• It DISPLAYS the requirements modules
• Choose REPORT: Analysis > reports > standard requirements report

To run reports from QC:

They saved AUTOMATICALLY when the USERS CLICKS on “END RUN” in the Test LAB.

They saved automatically when the users clicks on “END RUN” in the Test Lab.

By DEFAULT in the ORDER in which they were ADDED.

By default in the order in which they were added.

The interfaces of QC are:

• SITE ADMIN
• QUALITY CENTER

The interfaces of QC are:

There are 5 phases:

1. Specify releases.
2. Specify requirements.
3. PLAN tests.
4. EXECUTE tests.
5. TRACK DEFECTS.

There are 5 phases:

QUALITY Center live analyses GRAPH provides a visual overview of all tests WITHIN a FOLDER in test plan tree.

Quality Center live analyses graph provides a visual overview of all tests within a folder in test plan tree.

A table is a part of database which STORES RECORDS of INFORMATION about the test PLAN.

A table is a part of database which stores records of information about the test plan.

 We can map the requirements with test cases in QC:
1. In the requirements tab SELECT COVERAGE view.
2. Select requirement by clicking on parent/child or grandchild.
3. On RIGHT hand side another window will appear. It has TWO tabs:
(a) Tests coverage
(b) Details
Test coverage tab will be selected by default or you click on it.
4. 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.

 We can map the requirements with test cases in QC:
1. In the requirements tab select coverage view.
2. Select requirement by clicking on parent/child or grandchild.
3. On right hand side another window will appear. It has two tabs:
(a) Tests coverage
(b) Details
Test coverage tab will be selected by default or you click on it.
4. 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.

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.

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.

ROLES & responsibilities of QC Admin are:

• Project Creation
• MANAGING users and their authentication.
• Performance MONITORING.
• Data backup ETC.

Roles & responsibilities of QC Admin are:

ASSESSMENT REQUIREMENT represents requirements that are children of ANALYSIS requirement and at lower LEVEL in TREE hierarchy.

Assessment requirement represents requirements that are children of analysis requirement and at lower level in tree hierarchy.

We determine the RISK category for each assessment requirement under the analysis requirement, It has TWO factors:

1. BUSINESS CRITICALITY
2. Failure Probability.

We determine the risk category for each assessment requirement under the analysis requirement, It has two factors:

SQL SERVER is the default DATABASE in QUALITY Center.

SQL Server is the default database in Quality Center.

The USERS GROUP DETERMINES the PRIVILEGES that the user has within a PROJECT.

The users group determines the privileges that the user has within a project.

To SEE the records that MEET the specific CRITERIA that we DEFINE we use filters. We can define multiple ITEMS as Filter.

To see the records that meet the specific criteria that we define we use filters. We can define multiple items as Filter.

We NEED to SPECIFY the USERS and the PRIVILEGES for each USER.

We need to specify the users and the privileges for each user.

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.

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.

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:

• Checking Out Entities Automatically
• Checking Out Entities Manually

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:

In the defect TRACKING window of QC, there is a “FIND similar defect” icon. When this icon is CLICKED after writing the defect, if ANYBODY else has entered the same defect then it points it out.

In the defect tracking window of QC, there is a “find similar defect” icon. When this icon is clicked after writing the defect, if anybody else has entered the same defect then it points it out.

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.

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.

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.

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.

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.

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.

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.

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.

The DEFECT ID is AUTOMATICALLY generated after clicking SUBMIT button.

The Defect ID is automatically generated after clicking Submit button.

The Quality Center modules are:

1. RELEASE Module: Allows us creating a project release. Each release can have multiple cycles.
2. Requirement Module: Allows us in managing requirements LIKE what we are testing, what are the requirement topics and items and what are the analyzing requirements.
3. Test Plan: Allows us to write test cases for the requirements in a hierarchical tree-structure.
4. Test RESOURCES: Allows us in managing test resources. Tests resources can be associated with tests.
5. Test lab: Allows us to run tests and analyze the results.
6. Defect Module: Allows us to log all the failed test cases results.
7. DASHBOARD: Allows us to create graphs and reports.

The Quality Center modules are:

• QUALITY CENTER is a test management tool which can also manage Defects APART from other FEATURES.
• BugZilla is Defect Management tool only.

No, we don’t have PROGRAMMING INTERFACE in QUALITY CENTER.

No, we don’t have programming interface in Quality Center.

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.

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.

QUALITY Center 8.0 is the first VERSION and Quality Center or ALM 12.0 is the latest version.

Quality Center 8.0 is the first version and Quality Center or ALM 12.0 is the latest version.

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.

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.

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

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

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.

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.

Quality Center is SIMPLE and one of the best test management tool. Its benefits are:

1. It can be accessed through an IE browser.
2. Project database of a test can be maintained by QC.
3. It can be integrated with HP testing tools like QTP and Load Runner. It is ALSO compatible with third party tools.
4. It helps in effectively executing test sets, collecting results and analyzing data.
5. It helps in monitoring defects closely.
6. QC can be LINKED to an email system which provides an easy way to SHARE defect tracking information.
7. It can be used for creating reports and graphs which helps in analyzing test data.
8. It supports virtual environments like Citrix XenApp 6.0 and VMware ESX 5.0.

Quality Center is simple and one of the best test management tool. Its benefits are:

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.

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.