Professional Documents
Culture Documents
Test Director
application-testing process. One can also create reports and graphs to help review
the progress of planning tests, executing tests, and tracking defects before a
software release.
TestDirector connects requirements directly to test cases, ensuring that all the
requirements have been covered by the test cases.
application. It maps requirements directly to the test cases ensuring that all the
requirements have been covered by the test cases. It can import requirements and
test plans from excel sheet accelerating the testing
Filters in TestDirector are mainly used to filter out for the required results. It helps to
customize and categorize the results. For eg: to quickly view the passed and failed
tests separately filters are used.
5. What is Test Lab?
In the Test Lab the test cases are executed. Test Lab will always be linked to the test
plan. Usually both are given the same name for easy recognition.
Firstly one should collect all the attributes that has to be part of the defect
management like version, defect origin, defect details, etc. Later using the modify
options in QC one can change the defect module accordingly.
7. What is the advantage of writing test cases in Quality Center than writing in excel
sheet?
Although creating test cases in excel sheet will be faster than doing it in QC as excel
is more user friendly when compared to QC one require to upload them to QC and
this process may cause some delay due to various
reasons. Also QC provides link to other tests which in turn is mapped to the
requirements.
The main difference is QC is more secured than TestDirector. In Quality Center the
login page shows projects associated only to the logged in user unlike in Test
Director where one can see all the available projects.
Also test management is much more improved in QC than TD. Defect linkage
functionality in QC is more flexible when compared to TD.
Test instance is an instance of test case in Test Lab. Basically it means the test case
which you have imported in Test lab for execution.
Requirement module in TD is used for writing the requirements and preparing the
traceability matrix.
Yes one can attach the test data to the corresponding test cases or create a separate
folder in test plan to store them.
12. If one tries to upgrade from TestDirector 7.2 to QC 8.0 then is there risk of
losing any data?
No there is no risk of losing the data during the migration process. One has to follow
proper steps for successful migration.
Once the test cases are executed in the Test Lab and bugs are detected, it is logged
as a defect using the Defect Report Tab and sent to the developer. The bug will have
5 different status namely New, Open, Rejected,
Deferred and Closed. Once the bug has been fixed and verified its status is changed
to closed. This way the bug lifecycle ends.
14. In TD how are the test cases divided into different groups?
In the test plan of TestDirector one can create separate folder for various modules
depending on the project. A main module in the test plan can be created and then
sub modules be added to that.
TestDirector is a test management tool. In TD one can write manual and automated
test cases, add requirements, map requirements to the test cases and log defects.
Bugzilla is used only for logging and tracking the
defects.
Yes TestDirector and Quality Center are same. Version of TD 8.2 onwards was known
as Quality Center. The latest version of Quality Center is 9.2. QC is much more
advanced when compared to TD.
17. What is the instance of the test case inside the Test Set?
Test set is a place containing sets of test cases. We can store many test cases inside
test set. Now instance of test case is the test case which you have imported in the
test tab. If an another test case has the same
steps as this test case till half way then you can create the instance of this test case.
In TD reports are available for requirements, test cases, test execution, defects, etc.
The reports give various details like summary, progress, coverage, etc. Reports can
be generated from each TestDirector module
using the default settings or it can be customized. When customizing a report, filters
and sort conditions can be applied and the required layout of the fields in the report
can be specified. Sub-reports can also be added
to the main report. The settings of the reports can be saved as favorite views and
reloaded as required.
19. How can one map a single defect to more than one test script?
Using the ‘associate defect’ option in TestDirector one can map the same defect to a
number of test cases.
It is not possible to create ones own template for defect reporting in TestDirector but
one can customize the template that is already available in TestDirector as required.
Any automation script can be created directly in TD. You need to open the tool
(Winrunner or QTP) and then connect to TD by specifying the url, project, domain,
userid and password. And then you just record the script
like you always do. When you save the script, you can save it in TD instead of your
local system.
In the defect tracking window of TD 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.
The test grid displays all the relevant tests related to a project in TD. It contains the
some key elements like test grid toolbar with various buttons for commands which
are commonly used when creating and modifying
the tests, grid filter which displays the filter that is currently applied to a column,
description tab which displays a description of the selected test in the test grid and
history tab that displays the changes made to a test.
Defects which is used by the test engineers for logging the defects.
In order to upload data from excel sheet to TD firstly excel addin has to be installed,
then the rows in the excel sheet which has to be imported to TD should be selected,
and then finally the Export to TD option in the
There are 4 types of tabs available in TestDirector. They are Requirement, Test Plan,
Test Lab and Defect. It is possible to customize the names of these tabs as desired.
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.
Test Instance is used to run the test case in the test lab. It is the test instance that
you can run since you can’t run the test case in test set.
Quality Centre
1. What is meant by test lab in Quality Centre?
Test lab is a part of Quality Centre 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 Quality Centre 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 Quality Centre?
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 Quality Centre 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
3. how do you run reports from Quality Centre. Does any one have good white paper
or articles?
This is how you do it
1. Open the Quality Centre project
2. Displays the requirements modules
3. Choose report
Analysis > reports > standard requirements report
4. Can we upload test cases from an excel sheet into Quality Centre?
Yes go to Add-In menu Quality Centre, find the excel add-In, and install it in your
machine.
Now open excel, you can find the new menu option export to Quality Centre. Rest of
the procedure is self explanatory.
5. Can we export the file from Quality Centre 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.
Parent Requirements nothing but title of the requirements, it covers high level
functions of the requirements