自动化测试开发规则和标准.doc

Automated Testing Developing Standards Capitalization: DataTypes are always all uppercase. Examples: STRING, INTEGER. UnderScores are used in DataTypes that are multiple words. Examples: MY_ENUM, MY_RECORD. Hungarian notation is used for all variable names. The first letter of a variable name is the first letter(s) of its type. Examples: sUserName, iLoopCounter, lsProperties. Method and Function names begin with an uppercase letter. Each Significant letter is capitalized. Naming Conventions: Use the const SCRIPT_DIR to reference the path to 4Test scripts. If multiple directories are used, make these references relative to SCRIPT_DIR. The method used to invoke a window is called Invoke. The method used to close a window is called Close. The method used to accept a dialog is called Accept. Coding Conventions: Functions and Methods that do not return a value should be indicated by using the return type VOID. All methods and functions should end with a return statement even if it is VOID. All while loops that wait for a GUI event to terminate include a second expression/counter to prevent infinite loops. Example: iLoops = 1 while !MyWindow.Exists iLoops 60 … iLoops++ All switch statements have a default case, which may raise an error if no case is matched. Place reusable functions in a file called myapp_funcs.inc. Pathnames are never hard-coded. Instead use a const in a general.inc file that is either assigned explicitly or via an environment variable. Examples: const SCRIPT_DIR = “ { HOST_GetEnv ( “ SCRIPT_DIR” ) } ” const DATA_DIR = “ { SCRIPT_DIR }\data ” All included files are listed in a file called usefiles.inc. The main frame file for the application under test includes the statement use usefiles.inc. Include a single space between a method name and its argument list. There is no space between the parenthesis and the first and last arguments. Example: VOID Invoke (STRING sPath) The optional me