Testing Interview Questions

1. What is difference between master test plan and test plan?
Master plan is a document showing the planning for whole of the project i.e. all the phases of the project whereas the test plan is the document required for only testing people.

2. What is the main purpose of storing requirement in Test Director?
In test director(Requirement Tab) we stores our project requirement documents according to our modules or functionality of the applications. This hepls us to makes sores that all requirements are covered when we trace developed Test case/ test script to the requirements.

3. What are the 3 views and what is the purpose of each view?
The 3 views of requirements are:
1. Document view-tabulated view
2. Coverage view- establish a relationship between requirement and the test associated with them along with their execution status. Mostly the requirements are written in this view only.
3. Coverage analysis view-show a chart with requirement associated with the test and execution status of the test.

4. How many types of reports can be generated using Test director?
Reports on test director displays information about the 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 favorite views and reload them as needed.

Reports available in Requirements Module:
standard Requirements:
Tabular
Requirements with Coverage tests
Requirements with coverage tests and steps
Requirements with associated defects

Reports available in Test plan module:
Stan dared test planning
Subject tree
Tests with covered requirements
Tests with associated defects

Reports available in test lab module:
Current test set
Cross test set with tests
Current test set with failed test runs
Cross test set with failed test runs

Reports available in defects module:
Standard defects
Tabular defects
Defects with associated test and runs
Fixed or rejected defects detected by current user
Opened defects and assigned to current user

5.What does Test Grid contains?
The test Grid displays all the tests in a test director projects
The test grid contains the following key elements
Test grid tool bar, with buttons of commands commonly used when creating and modifying the test grid.
Grid filter, displaying the filter i.e. currently applied for a column
Description Tab: Displaying a description of the selected test in the test grid.
History Tab, displaying the changes made to a test. For each change the grid displays the field name, data of change, name of the person who made the change, and the new value.

6. How will you generate the defect ID in test director? Is it generated automatically or not?
When you will add a new defect and submit it to test director it will generate a new ID for that defect.
The defect ID automatically generate after we click submit button.

7. Difference between TD8.0 and QC8.0?

Subject

Test director8.0

Quality Center8.0

Technology

C++, IIS, COM

Back-end is Java based, runs on application server

Operating systems

Microsoft Windows

Ms windows, Red Hat Linux and Solaris

clustering

single server only

Full clustering support

Database connectivity

Requires Database client installation, ADO interface

Does not require database client installation. Direct access to a database server using a JDBC type 4 driver

Repository

Domain repository(TD_Dir)

Repository divided into to sub-directories. QC directory for default and user defined domains. SA directory for site administrator data.

Virtual directory

Virtual directory name is tdbin

Quality center server virtual directory name is qcbin. Site administrator server virtual directory name is sabin.

Supported databases

Microsoft Access, Microsoft SQL, Oracle, Sybase

Microsoft SQL, Oracle

Site administrator data(domains, projects and users)

Data stored in the doms.mdb file

Data stored in the site administrator schema on a database server

Common settings

Data stored in the file system

Data stored in the database

User authentication

Windows authentication

LDAP authentication

8. How do you ensure that there are duplication of bugs in test director?

In the defect tracking window, at the top we can find the similar defect icon, If we click after writing our defect, if any of the tester already added the similar defects it will tell else we can add.

9. How you integrated your automated scripts from test director?

When you work with winrunner you can choose to save your tests directly to your test director database or while creating a test case in the test director we can specify whether the script in automated or manual. And if it is automated script then test director will build a skeleton for the script that can be later modified into one which could be used to test the AUT.

Related Posts

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.