Silk Test Classic uses the following types of files in the automated testing process, each with a specific function. The files marked with an * are required by Silk Test Classic to create and run test cases.
Silk Test Classic projects organize all the resources associated with a test set and present them visually in the Project Explorer, making it easy to see, manage, and work within your test environment.
The project file has a Verify Test Project (.vtp) extension and is organized as an .ini file; it stores the names and locations of files used by the project. Each project file also has an associated project initialization file: projectname.ini.
|Exported Project||.stp||A Silk Test Project (.stp) file is a compressed file that includes all the data that Silk Test Classic exports for a project. A file of this type is created when you click . The .stp file includes the configuration files that are necessary for Silk Test Classic to set up the proper testing environment.|
|Testplan||.pln||An automated test plan is an outline that organizes and enhances the testing process, references test cases, and allows execution of test cases according to the test plan detail. It can be of type masterplan or of subplan that is referenced by a masterplan.|
|Test Frame*||.inc||A specific kind of include file that upon creation automatically captures a declaration of the AUT’s main window including the URL of the Web application or path and executable name for client/server applications; acts as a central repository of information about the AUT; can also include declarations for other windows, as well as application states, variables, and constants.|
|4Test Script*||.t||Contains recorded and hand-written automated test cases, written in the 4Test language, that verify the behavior of the AUT.|
|Data-Driven Script||.g.t||Contains data-driven test cases that pull their data from databases.|
|4Test Include File||.inc||A file that contains window declarations, constants, variables, classes, and user defined functions.|
|Suite||.s||Allows sequential execution of several test scripts.|
|Text File||.txt|| An ASCII file that can be used for the following:
|Results File||.res||Is automatically created to store a history of results for a test plan or script execution.|
|Results Export File||.rex||A single compressed results file that you can relocate to a different machine. Click .rex file out of the existing results files of a project.to create a|
|TrueLog File||.xlg||A file that contains the captured bitmaps and the logging information that is captured when TrueLog is enabled during a test case run.|
|Keyword-Driven Test File||.kdt||An executable file which contains keywords. Keyword-driven test files are used when testing with the keyword-driven testing methodology.|
|Keyword Sequence||.kseq||A keyword-sequence file contains a combination of keywords, which are always executed in the same order. A keyword-sequence file cannot be executed on its own, only when included in a keyword-driven test. In context of a keyword-driven test, a keyword-sequence can be used as any other keyword. Keyword sequence files are used when testing with the keyword-driven testing methodology.|