0
|
1 |
The .bat and .txt files in directories Batchfiles and CommandFiles has
|
|
2 |
been automatically generated by the Perl script
|
|
3 |
DABS_test_data.pl. That script uses a files called test_data.txt to
|
|
4 |
read which batch files copies over test data from the MMC card to the
|
|
5 |
C:-drive and delete the data from the C:-drive when test has
|
|
6 |
finished.
|
|
7 |
|
|
8 |
test_data.txt was generated by executing "grep -i -l copy *.bat
|
|
9 |
>test_data.txt" in a Cygwin bash shell. The grep utility found on
|
|
10 |
\\londata21\tools works just as well.
|
|
11 |
|
|
12 |
The .txt files contain the command autoexec.bat will execute on HW to
|
|
13 |
copy over the data. Eg MMFSbcUnitTests_del_data.txt contains the line:
|
|
14 |
|
|
15 |
call e:\MMFSbcUnitTests_del_data.bat
|
|
16 |
|
|
17 |
The .bat files contains the actual copy and delete commands.
|
|
18 |
|
|
19 |
These files are necessary because the DABS system uses one file to
|
|
20 |
build up the autoexec.bat file. A line in that file can look like:
|
|
21 |
|
|
22 |
testframework, logs\testresults\mm\TSU_MMF_SBCCODEC.htm, ,
|
|
23 |
\TSU_MMF_SBCCODEC.script, 600, UREL,
|
|
24 |
MMFSbcUnitTests_copy_test_data.txt,
|
|
25 |
MMFSbcUnitTests_del_test_data.txt
|
|
26 |
|
|
27 |
where the two last arguments is the pretest and posttest command
|
|
28 |
files. Unfortunately the command file can only contain one line as
|
|
29 |
the DABS system only reads the first line in that file. Bonkers
|
|
30 |
but there you go.
|
|
31 |
|
|
32 |
The above test line will produce an autoexec.bat looking like this:
|
|
33 |
|
|
34 |
call e:\MMFSbcUnitTests_copy_test_data.bat
|
|
35 |
RUNTESTS testframeworkTSU_MMF_SBCCODEC.script.txt -t 10
|
|
36 |
call e:\MMFSbcUnitTests_del_test_data.bat
|