Difference between revisions of "Wildcard File"
| Line 1: | Line 1: | ||
| − | {{Idiomas|Archivo Wildcard|Wildcard File}} | + | {{Idiomas|Archivo Wildcard|Wildcard File|ワイルドカードファイル}} |
This wildcard is particularly useful as we want to employ the contents of a text file in a test case, for instance, as we need to fill in a text field which is quite lengthy, and we prefer to handle it outside the datapool. | This wildcard is particularly useful as we want to employ the contents of a text file in a test case, for instance, as we need to fill in a text field which is quite lengthy, and we prefer to handle it outside the datapool. | ||
Latest revision as of 19:05, 22 March 2016
 |
 |
 |
This wildcard is particularly useful as we want to employ the contents of a text file in a test case, for instance, as we need to fill in a text field which is quite lengthy, and we prefer to handle it outside the datapool.
Using values from files
Taking into account that both, either Datapools, or the text fields may be uncomfortable to work with large amount of characters (for instance, an xml), the value a command will use may be loaded from a file in the hard drive. Throughout its execution, GXtest will use the text from within the file regardless the formatting of its content.
The syntax of the value is the following:
%FILEPATH_WILDCARD%<path_to_the_file>
For instance, in order to use in a FillInput, the value contained in the file c:\temp\archive.xml, the following value must be used %FILEPATH_WILDCARD%c:\temp\archivo.xml
Such value may be used in either a variable, a Datapool, or directly as a value for the command.
Its use is not case sensitive, and it's addressed for using with:
- the value typed in a FillInput command
- the parameters of a WebService invocation
Bear in mind that, for running a test in a GXtest Executor, the file must be available, either locally, or through a valid and available path in the network.
