Test form naming convention
Test forms are test frameworks and test engineers must use and process. It contains functional operations for each test, so you must comply with certain naming regulations, otherwise the test engine cannot identify and do not know how to handle it.
For example, you have adding a test case Verify Login Window in Heigh_level, which is the same as a name file with the test case name in Heigh_level, provides DDE engine processing as Verify login window.xxx. The extension is the engine automatically added, and each test engine knows what the extension name of the file should look like. If you have changed your file suffix, you can use this Verify login window.ext.
The following is a file name in each level:
One. CYCLE table ".cdd"
When you don't specify the test form extension name for the CycleDriver engine, the CYCLE table default extension name is .cdd. The CYCLE table is the highest level of test form that needs to be processed. This table contains not only the Suite test form that calls the SuiteDriver engine, but also the function of performing other Cycledriver commands.
When the CYCLE table contains a test case, such as login, this is actually CycleDriver tune SuITedriver and processes the file Login.Std from the SuiteDriveer engine. (SuiteDriver test form is .STD)
two. Suite form ".std"
Also when you don't specify the test form extension name for the SuiteDriver engine, the Suite table default extension name is .STD. The Suite form is a scheduled table that needs to be processed. This table not only contains the STEP test form that calls the StepDriver engine, but also contains functions that perform other suitedriver commands.
When the suite table contains a test case, for example, "Verify Login Title", this is actually SuiteDriver calls the StepDriver engine and processes the "Verify login title.sdd" file by Stepdriver. (The default name for the StepDriver test form is .sdd)
three. STEP form ".sdd"
If you don't specify the test form extension name for the StepDriver engine, the STEP form default extension name is .sdd. The STEP form is a low-level hierarchy that needs to be processed. This table contains not only the component functions and tool scripts that call the StepDriver engine, but also contain driver command functions that perform other StepDriver hierarchy.
When you use Excel or other tables in other file formats, then the best follow-up name agreement, each file has a thin name contains a file extension name. When the engine processes the table, export each work-thin content to the file that is the same as the current work.
Example: In Excel Work Thin Name
CYCLE: "regression.cdd"
Suite: "Perform Login Tests.std"
Suite: "Perform Main Window Tests.std"
Step: "verify login title.sdd"
Step: "Verify Main Title.sdd"
