Professional Documents
Culture Documents
The following table highlights the main differences between Test Director 8.0 and Quality
Center 8.0.
• Solaris
Koinmnm
• Sybase
Site Administrator Data Data stored in the doms.mdb Data stored in the Site Administrator
(domains, projects, and users) file schema on a database server
Common Settings Data stored in the file system Data stored in the database
Click on the New Defect to post the defect in the issues section and add the description,
Summary, details of the defect like O/s, to whom the defect is concerned , severity and the
product version etc and click on the submit button - the defect Id is generated automatically.
Reports on Test Director display information about test requirements, the test plan, test runs,
and defect tracking. Reports can be generated from each Test Director module using the
default settings, or you can customize them. When customizing a report, you can apply filters
and sort conditions, and determine the layout of the fields in the report. You can further
customize the report by adding sub-reports. You can save the settings of your reports as
favourite views and reload them as needed.
Standard Requirements:
Tabular
Subject tree
Standard defects
Tabular defects
3. Testlab -> to execute the test sets & track the results
1. Parent requirement
2. Child requirement
Parent requirement is nothing but Title of the requirements its covers high level functions of
the requirements.
Child requirement is nothing but sub - Title of the requirements its covers low level functions
of the requirement. OR
You can add requirements to test cases in two ways; either from Requirements tab or Test
Plan tab. Navigate to the appropriate Requirement and right click, you can find the menu to
map the test case and the vice versa is available in Test plan tab. OR
In the test plan view, click on the required test plan, on the window pan click on the Req.
coverage tab, to add click on the 'select red' icon(2nd row, first from the left). A list of
requirements will open to the right. Select any requirement you want to link to this particular
test case and click on the left arrow key on this window. The particular req. would be linked to
this particular test case.
1. Export the test cases in to Test Director. (It will contain total 8 steps).
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 graphs in the test lab for daily report and sent to the onsite (where ever you want to
deliver).
5. If you got any defects and raise the defect in the defect module. When raising the defect,
attach the defect with the screen shot.
(ii) If you want to start from the scratch, you have to create business requirement through the
req. tab of test director. It can have main requirements and subsequent child requirements.
Once you create and get it approved, you are ready to start creating test plan and test cases
for each and every individual business requirement.
2> There may be many test plans. For every test plans there may be many test cases. Start
with creating test plan for every business requirement, starting from the main
requirement, develop corresponding test plans. Every parent test plan will have child test plan
for every corresponding child requirement.
3> Once the test cases and design scripts are developed, transfer them into test lab. Where
they can be run as manual or automated test cases.
4>for each run of the test case, you can report a defect and enter into defect report on defect
tab.
Chose report
The main purpose for storing requirements in test director is to ensure 100% test coverage of
the requirement. You can create a test plan/tests which if done correctly can be automatically
mapped to the requirements. So the end result would be that once an individual runs the test
selected in the test lab, it will show not only the coverage but also pass/fail/no runs.
Purpose to storing requirement in TD is it keeps the testing effort on track and measures the
application against business-user needs. Test Director’s Requirements Manager links test cases
to application functional requirements, ensuring traceability throughout the testing process.
Using TD, you can easily see what percentage of the application functional requirements are
covered by tests, how many of these tests have been run, and how many have passed or
failed.
Link -> now click on Microsoft Word Add-in - >click on Download Add-in (build number
8.0.1.512) to download the add ins.