How can I check if a environment variable exist or not?
When we use Environment("Param1").value then QTP expects the environment variable to be already defined. But when we use Environment.value("Param1") then QTP will create a new internal environment variable if it does not exists already. So to be sure that variable exist in the environment try using Environment("Param1").value.Reply
What is the main purpose of storing requirements in Test Director?
In TestDirector (Requirement Tab) We Stores Our Project Requirement documents according to our modules or functionality of the applications. This helps us to makes sures that all requirements are covered when we trace developed Test Case/Test Script to the requirements. This helps QA Manager to review what extent the requirements are covered. Reply
What are the 3 views and what is the purpose of each view?
The 3 views of requirment are:
1) Document View-tabulated view
2) Coverage View-establish a relationship between requirement and the test assosiated with them along with their execution status.Mostly the requirements are written in this view only.
3) Coverage analysis view-show a chart with requirementassociated with the test,and execution status of the test. Reply
How many types of reports can be generated using TestDirector?
Reports on TestDirector display information about test requirements, the test plan, test runs, and defect tracking. Reports can be generated from each TestDirector module using the default settings, or we can customize them. When customizing a report, We can apply filters and sort conditions, and determine the layout of the fields in the report. We can further customize the report by adding sub-reports. We can save the settings of our reports as favorite views and reload them as needed.Reply
Difference between WinRunner and Test Director?
Many diff are there :
> WinRunner : Its an Automation Testing tool, used for automation of manual written Test Cases to Test Scripts and Regression Test also.
> Test Director : Its an Testing Management tool, used from Creating Test Plan,Preparation of testCases, Execution of testcases and generating defect report.Also used for maintaining Test Scripts. Reply
How will you generate the defect ID in test director? Is it generated automatically or not?
The Defect ID will be Generated Automatically after the submission of the defect.Reply
How to add Test ID to TestPlan?
Create an object with a type = Number.
Name it something like "Test_ID" in the Customize Entities area. Then go into the Workflow Script Editor to "TestPlan module script/TestPlan_Test_MoveTo" and insert the following :
If Test_Fields.Field("Our Object Name").Value <> Test_Fields.Field ("TS_TEST_ID").Value then Test_Fields.Field("Your Object Name").Value = Test_Fields.Field("TS_TEST_ID") .Value end if
This will put an object on each test thet displays the Test ID Number.Reply
What is the difference between Master test plan and test plan??
many diff are there :
> Master test plan is the doccumaent in which each and every functional point is validated.
> Test case docuument contains test cases, Test case is the perception with which probability of finding the defect is more.Reply
How to generate the graphs in Test Director ?
Open test director and then click the Analysis we will find three type of graphs :
> Planning Progress Graphs.
> Planning Summary Graphs.
> Defect Age Graph.
Click any of one and we can generate the graphs. The generation of graphs in the Test Director that to Test Lab module is :
> Graph Wizard.
> Select the graph type as Summary and click the Next button.
> Select the show current tests and click the next button.
> Select the Define a new filter and click the Filter button.
> Select the test set and click the Ok button.
> Select the Plan : subject and click the ok button.
> Select the Plan: Status.
> Select the test set as x-Axis.
> Click the Finish button.Reply
What does Test Grid contains ?
Test Grid contains bassically :
> The Test Grid displays all the tests in a TestDirector project.
> The Test Grid contains the following key elements:
> Test Grid toolbar, with buttons of commands commonly used when creating and modifying the Test Grid.
> Grid filter, displaying the filter that is currently applied to 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, date of the change, name of the person who made the change, and the new value. Reply