WinRunner: Documentation:

WinRunner: Documentation:

> Each test procedure should have a manual test plan associated with it.

> Use word to write the detailed test plan information.

> When test planning is completed cut and paste (or translate) the test plans into test director.

> When creating folders, tests and test sets in Test Director make sure every item has as description.

> When creating test scripts, cut and paste the default header script:


###########################################################

# Script Name:

# Description:

#

# Project:

# #########################################################

# Revision History:

# Date: Initials: Description of change:

#

###########################################################

# Explaination of what script does:

#

#

###########################################################

#this is here for debugging only, when run in shell script

#will comment out.

#reload (\"J:\\CorpQATD\\TD_Daybr\\functions\\functions\");

{put code here}


#this is here for debugging only, when run in shell script #will comment out.

#unload (\"J:\\CorpQATD\\TD_Daybr\\functions\\functions\");

> Before any automation project is started, the tester will write an automation standard document. The automation standards document will describe the following:

> Automation Environment

> Installation requirements

> Client Machines Configurations

> Project Information

> WinRunner Option Settings

> Identify Servers, Database and Sub System tests will run against

> Naming Convention for project

 Specific Recording Standards that apply to individual project.

> While Scripting please comment major portions of the script using WinRunner\'s comment command \"#\" . (example: #This is a comment.) 


By:UMANG
Date:2003-02-09 00:00:00

Post Your Answers


User Email:

User Name:
Answers:

Related TESTING Subjective Links

TESTING Subjective interview questions and answers for experienced and fresher