1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/os/mm/mmtestenv/mmtesttools/Scripts/DABS/readme.txt	Fri Jun 15 03:10:57 2012 +0200
     1.3 @@ -0,0 +1,36 @@
     1.4 +The .bat and .txt files in directories Batchfiles and CommandFiles has
     1.5 +been automatically generated by the Perl script
     1.6 +DABS_test_data.pl. That script uses a files called test_data.txt to
     1.7 +read which batch files copies over test data from the MMC card to the
     1.8 +C:-drive and delete the data from the C:-drive when test has
     1.9 +finished. 
    1.10 +
    1.11 +test_data.txt was generated by executing "grep -i -l copy *.bat
    1.12 +>test_data.txt" in a Cygwin bash shell. The grep utility found on
    1.13 +\\londata21\tools works just as well. 
    1.14 +
    1.15 +The .txt files contain the command autoexec.bat will execute on HW to
    1.16 +copy over the data. Eg MMFSbcUnitTests_del_data.txt contains the line:
    1.17 +
    1.18 +call e:\MMFSbcUnitTests_del_data.bat
    1.19 +
    1.20 +The .bat files contains the actual copy and delete commands.
    1.21 +
    1.22 +These files are necessary because the DABS system uses one file to
    1.23 +build up the autoexec.bat file. A line in that file can look like:
    1.24 +
    1.25 +testframework, logs\testresults\mm\TSU_MMF_SBCCODEC.htm, ,
    1.26 +\TSU_MMF_SBCCODEC.script, 600, UREL,
    1.27 +MMFSbcUnitTests_copy_test_data.txt,
    1.28 +MMFSbcUnitTests_del_test_data.txt 
    1.29 +
    1.30 +where the two last arguments is the pretest and posttest command
    1.31 +files. Unfortunately the command file can only contain one line as
    1.32 +the DABS system only reads the first line in that file. Bonkers
    1.33 +but there you go.
    1.34 +
    1.35 +The above test line will produce an autoexec.bat looking like this:
    1.36 +
    1.37 +call e:\MMFSbcUnitTests_copy_test_data.bat
    1.38 +RUNTESTS testframeworkTSU_MMF_SBCCODEC.script.txt -t 10
    1.39 +call e:\MMFSbcUnitTests_del_test_data.bat