Quality Center or Test Director Installation Guide

What is Quality Center:
HP TestDirector for Quality Center offers a single, web-based application that supports all essential aspects of test management. It provides a consistent, repeatable process for gathering requirements, planning and scheduling tests, analyzing results and managing defects and issues. This software enables your organization to digitize specific quality processes and procedures within the larger application lifecycle. It also supports high levels of communication and collaboration among your IT team.

Key features:

• Access testing assets anytime, anywhere via a browser interface
• Create an end-to-end quality management infrastructure
• Manage manual and automated tests.
• Accelerate testing cycles by scheduling and running tests automatically, unattended, 24x7
• Analyze application readiness at any point in the testing process with integrated graphs and reports

Installation Process Guide with Screenshots:

View Demo:

See Here >>>>

Don't miss any article:Get it by E-mail

Mercury Quality Centre(Test Director)

Mercury Quality Center is a web-based test management tool. It gives you a centralized control over your entire testing Project. It can make the task of the testers and managers easy by giving an easy interface to manage and organize activities like Requirements coverage, Test Case Management, Test Execution Reporting, Defect Management, and Test Automation. All these activities are provided from a single tool, which is web-based and can be accessed from any where. Mercury Quality Centre can be divided into two parts. One for tool administrator and another for tool user. These two parts are called Site Administrator Bin and Quality Centre Bin. These parts are discussed in more detail in the next section.

Site Administration Bin ( SABin ) : This is an important part of the software and also starting point for the usage of Mercury Quality Centre project. All the administrative activities like creating the projects, assigning users to the projects, creating specific roles etc. is done from this area. This section is also used for configuring your application with the tool. For example, if you want to use the Winrunner or Quality Test Professional ( QTP ) scripts from Quality Center, you need to specify it here. If you are using Winrunner, you need to make sure that backward compatibility property of the application to true. SABin can also be used to configure the mail servers. Password for site admin is defined during the installation so make sure that you remember the password during installation.

Quality Center Bin ( QCBin ) : This is how user interact with tool. QCBin interface gives functionality of creating test plans, defining requirements, creating test cases, creating test labs, associating requirements with defects in essence, everything that as a tester or test manager you need to do in your day to day activity apart from execution.

This article will start off with the explanation about SABin and then move towards using Quality Center using the QCbin.

Quality Centre is installed as a service in your windows environment. Before start working on it, make sure that Mercury Quality Centre service is running. As mentioned earlier, Quality Centre can be accessed from web browser using http://:8080/sabin/SiteAdmin.htm format, assuming that Quality Centre is listening on default port. This page is the starting point and gives a login screen where you need to provide admin credential which were used during the installation of Mercury Quality Centre. Once you are logged on to the SABin, you can perform all the administrative tasks mentioned above. You can also verify your licensing information, information about database etc. using SABin.

After you are done with defining your projects, user etc. it is time for QCBin to come into the picture. This is the most common interface used by the customers or users. Quality Center provides the role based accessed to the Projects. For example, A Test Manager can create projects and Test Lead can prepare test plans and tester can write the test cases. This role based access makes it very easy to control access to various artifacts of the project and also distribution of responsibility among team members.

There are four distinct things which can be managed in Mercury Quality Centre :

1. Requirements
2. Test Plan
3. Test Lab
4. Defects

These four items can be termed as the 4 pillars of the Quality Process for any organization. Each of these components sections contain information about different projects created using SABin.

Hope you have got good knowledge of Mercury Quality Centre on the above. To take it further, let us explore functionality of QCBin in step by step manner.

• Create a test project in SABin.
• Now log on to QCBin by providing your credentials and access the project that you have created.
• After you log in to the QCBin you will notice different tabs for requirement, TestPlan, TestLab and Defects.
• Click on the Requirements tab. Under this tab, you can organize your project requirements. You can also create folder hierarchy to represent various features in your project. This can be accomplished by just right-clicking and choosing appropriate options.
• After you have created new requirements its time for the Test Plan. Test Plan will have information about the test cases. These test cases can also be mapped to requirements created in the earlier steps, thus makes foundation for the traceability metrics.
• Each requirement can be mapped to one or more than one test cases. After creating new test case you will see in the left hand pane. The right hand pane will have tabs for writing the steps, mapping to requirements, description, expected result etc.
• Every test case will have steps and for every step you can specify the expected behavior. These test cases can also be linked to the QTP or Winrunner Scripts, thereby providing you better management for the automation and capability of executing automation scripts from Quality Centre itself.
• After the Test Plan preparation its time for the Test Execution. You have to create a Test Lab for managing test execution for specific release. Test Labs can be created, specific to the release and execution of test cases specific to release can be managed very easily using this concept.
• In the Test Lab you can identify the set of test cases already written under test plan to include for execution. These test cases are already linked to the requirement so after each test cycle the management will be able to trace what requirements have been tested.
• Automated Tests can be fired from Test Lab if you have integration with QTP in place. When you choose the option of manual test execution, a window will open up containing the steps to execute. These steps are executed and after every step you can specify whether it is passed or not. Quality Center also allows parameterized manual test execution, where some of the default parameters like username, password etc. can automatically be read during the manual execution. For example, suppose you have a template test which logs in a user with a specific password when you start your application, you need to call this test at the beginning of each test. In some cases, you will want to log in as a regular user while in others, you will need to log in as the administrator. You can therefore create two parameters, <> and <>, and change the value according to which type of test is calling your template test.
• The defects encountered during the failure of any of the steps can automatically be logged in to the defect tracking system, already integrated with Quality Centre.
• After the Test Execution the important part is Defects :) As already mentioned, this is integrated with the Qulaity center and incase of any failure from the manual or automated tests, defects can be logged.
• One of the most important part of the test management is generating reports. After all the planning and execution, its REPORTING time. Quality Center provides a very good reporting feature by providing certain pre-defined reports and also capability to create your own reports.

Hope information provided above would have provided you a good overview about Mercury Quality Center.

So lets test yourself with the Quality Center interview questions asked in different Companies

So lets start to look at questions:Part I >> and Part II>>

Don't miss any article:Get it by E-mail

Test Director Interview Questions Part1 »

Test Director Interview Questions: Part I
1. How many types of tabs in Test Director?
There are 4 tabs available in Test Director.

1. Requirement
2. Test plan
3. Test lab
4. Defect

We can change the name of Tabs, as we like. Test Director enables us to rename the Tab. In TD there only 4 tabs are available.

2. How to generate the graphs in Test Director?

The generation of graphs in the Test Director that to Test Lab module is:

1. Analysis
2. Graph
3. Graph Wizard.
4. Select the graph type as summary and click the next button.
5. Select the show current tests and click the next button.
6. Select the define a new filter and click the filter button.
7. Select the tests set and click on the ok button
8. Select the plan: subject and click on the Ok button.
9. Select the plan:status.
10. Select the test set as X axis.
11. Click the finish button.

3. How can we export multiple test cases from TD in a single go?

If we want to export it to any office tools

1. Select the multiple steps/cases you need.
2. Right click > save as and proceed.

4. How to upload test cases from excel into test director?

First we have to activate excel in test director with the help of adding page. After activation we can view the option as ‘export to test director’ in excel under tools tab.If you select the export to test director pop up dialog box opens the following process should be followed i.e.,

Enter

1. URL of Test Director
2. Domain name and project name
3. User name and password
4. Select anyone of these 3 options: Requirements or test cases or defects
5. Select a map option. a)select a map b)select a new map name c)create a temporary map.
6. Map the test director to corresponding excel. Map the field whatever you mention in excel.

These are the required steps to export the excel into TD.

5. Does anyone know of any integration between Test director and Rational Robot?

Any idea on the technical feasibility of such integration and level of effort would also be interesting?Test Director is software management tool. It is a Mercury Interactive Product.Rational Robot is a Rational product. It comes included with ‘test manager’ module for software management.Integrating the test director and Rational Robot is not feasible.

6. Explain the project tree in test director?

Project Tree in test director : Planning tests –Create test– execute tests–tracking defects.

7. What is coverage status, what does it do?

Coverage status is percentage of testing covered at a given time. If you have 100 test cases in a project and you have finished 40 of test cases out of total test cases then your coverage status of project is 40%. Coverage Status is used to keep track of project accomplishment to meet the final deadline of the deliverables.

8. Difference between data validation and data integrity?

Data Validation: We check whether the input data/output data is valid in terms of its length, data type etc..Data Integrity: We check out database contains only accurate data. We implement data integrity with the help of integrity constraints. So in data integrity we check whether the integrity constraints or implemented correctly or not

9. What are the uses of filters in test director?

Limits the data displayed according to the criteria you specified.

For Ex: You could create a filter that displays only those tests associated with the specified tester and subject.

Each filter contains multiple filter conditions. These are expressions that are applied to a test plan tree or to the field in a grid. When the filter is applied, only those records that meet the filter conditions are displayed.

You create and edit filters with the filter dialog box.This opens when you select the filter command. Once you have created a filter, we can save it for future use.

10. How do we generate test cases through test director?

Test lab we do the design step. Design grid we create parent child tree.

Ex: Database operation (test name)

1. Delete an order

Description: Click delete button to delete the order.

Expected results: Order is deleted.

Pass/Fail:Update an order

create an order.

Don't miss any article:Get it by E-mail

Test Director(Quality Center) Interview Questions Part2

Test Director Interview Questions:PartII
1. What is meant by test lab in test director?
Test lab is a part of test director where we can execute our test on different cycles creating test tree for each one of them. We need to add test to these test trees from the tests, which are placed under test plan in the project. Internally test director will refer to this test while running then in the test lab.
2. Can you map the defects directly to the requirements(Not through the test cases) in the test director?
In the following methods is most likely to used in this case:
Create your Req.Structure
Create the test case structure and the test cases
Map the test cases to the App.Req
Run and report bugs from your test cases in the test lab module.

The database structure in test director is mapping test cases to defects, only if you have created the bug from Application. test case may be we can update the mapping by using some code in the bug script module(from the customize project function), as per as i know, it is not possible to map defects directly to an requirements.
3. how do you run reports from test director. Does any one have good white paper or articles?
This is how you do it1.

1. Open the test director project
2. Displays the requirements modules
3. Choose reportAnalysis > reports > standard requirements report

4. Can we upload test cases from an excel sheet into test director?

Yes go to Add-In menu test director, find the excel add-In, and install it in your machine.Now open excel, you can find the new menu option export to test director. Rest of the procedure is self explanatory.

5. Can we export the file from test director to excel sheet. If yes then how?

Requirement tab: Right click on main req/click on export/save as word, excel or other template. This would save all the child requirements

Test plan tab: Only individual test can be exported. no parent child export is possible. Select a test script, click on the design steps tab, right click anywhere on the open window. Click on export and save as.

Test lab tab: Select a child group. Click on execution grid if it is not selected. Right click anywhere. Default save option is excel. But can be saved in documents and other formats. Select all or selected option

Defects Tab: Right click anywhere on the window, export all or selected defects and save excel sheet or document.

6. How many types of tabs are there in test director. Explain?

There are four types of tabs are available

1. Requirement : To track the customer requirements
2. Testplan : To design the test cases and to store the test scripts
3. test lab : To execute the test cases and track the results.
4. Defect : To log a defect and to track the logged defects

7. How to map the requirements with test cases in test director?

1. In requirements tab select coverage view
2. Select requirement by clicking on parent/child or grandchild
3. On right hand side(In coverage view window) another window will appear. It has two tabsa) Tests coverageb) DetailsTest 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 cans elect any test case you want to map with your requirements.

8. How to use test director in real time project?

Once completed the preparing of test cases

1. Export the test cases into test director( It will contained total 8 steps)
2. The test cases will be loaded in the test plan module
3. Once the execution is started. We move the test cases from test plan tab to the test lab module.
4. In test lab, we execute the test cases and put as pass or fail or incomplete. We generate the graph in the test lab for daily report and sent to the on site (where ever you want to deliver)
5. If we got any defects and raise the defects in the defect module. when raising the defects, attach the defects with the screen shot.

9. Difference between Web Inspect-QA Inspect?

QA Inspect finds and prioritizes security vulnerabilities in an entire web application or in specific usage scenarios during testing and presents detail information and remediation advise about each vulnerability.Web Inspect ensures the security of your most critical information by identifying known and unknown vulnerabilities within the web application. With web Inspect, auditors, compliance officers and security experts can perform security assessments on a web enabled application. Web inspect enables users to perform security assessments for any web application or web service, including the industry leading application platforms.
10. How can we add requirements to test cases in test director?

Just you can use the option of add requirements.Two kinds of requirements are available in TD.

1. Parent Requirement
2. Child requirements.

Parent Requirements nothing but title of the requirements, it covers high level functions of the requirements
Child requirement nothing but sub title of requirements, it covers low level functions of the requirements.

Don't miss any article:Get it by E-mail