Lines Matching refs:file
50 * `buildsolution.sh` is converting the solution file, using `csolution`, to generate the `.cprj` f…
89 #### R1 : The tests shall be described in a file
151 A test description file is defined with a specific syntax to support R1 to R8.
194 …now where is the data and how to get it, this information is provided in the test description file.
214 The file is in the folder defined with the folder properties of the group / suites.
253 There are 2 ways. First way is a parameter file. Problem of a parameter file when it has to be incl…
255 Those parameters values, when specified with a file, are described with:
396 ### Generate the cpp,h and txt files from the desc.txt file
409 This will create a file `Output.pickle` which is containing a Python object representing
410 the parsed data structure. It is done because parsing a big test description file is quite slow.
412 So, it is needed to be done only once or if you modify the test description file.
459 * `buildsolution.sh` is converting the solution file, using `csolution`, to generate the `.cprj` f…
472 The `-f` option should be used to tell the script where to find the `Output.pickle` file if the scr…
492 The file result.txt must be placed inside the build folder for this script to work.
493 Indeed, this script is using the path to result.txt to also find the file currentConfig.csv which h…
496 The Output.pickle file is used by default. It can be changed with -f option.
585 For a test suite MyClass, the scripts are generating an include file MyClass_decl.h
587 You should create another include Include/MyClass.h and another cpp file Source/MyClass.cpp in TEst…
603 // Definitions of the patterns you have in the test description file
756 * The corresponding float16_t tests are put in a different test file desc_f16.txt