- echo "Usage: $0 <test stuff directory> [-s]"
- echo
- echo " Performs test case programming from scratch (current test cases will be dropped from ADML involved instances)."
- echo
- echo " test stuff directory: contains msk files, specially a testcase description with xml files referenced."
- echo " Those files, adding .msk extension, shall exists in the same directory. For example:"
- echo
- echo " $0 st_examples/DynamicQualification"
- echo
- echo " -s: start testing just after programming, using desired rate: $DESIRED_RATE test cases per second."
+ cat << EOF
+Usage: $0 <test stuff directory|dynamic> [-s]
+
+ Performs test case programming from scratch (current test cases will be dropped
+ from ADML involved instances). There are two types of programming depending on
+ the first argument provided:
+
+ test stuff directory:
+
+ The folder provided must contain msk files, specially a testcase file with
+ xml files referenced inside. Those xml files (without the .msk extension)
+ shall exists in the directory. For example:
+
+ $0 st_examples/DynamicQualification
+
+ Optionally, a file 'specific' could exists containing testcase-specific
+ information, which normally will be used to specify database sentences.
+ This file will be accumulated as a cloning seed over the file 'specific.all'
+ created on test stuff directory.
+
+ Template type programming could be used for medium-duration testings, because
+ the scripting used for programming, have lots of groups divisions which even
+ background-executed are much more slower on programming than a c++ builtin
+ procedure: dynamic type is the one for large sets of test cases:
+
+
+ dynamic:
+
+ The current dynamic procedure selected by mean 'dynlibs/select.sh' script,
+ will be programmed using its dirname resources: inside, you may found not
+ only the .so library but the needed xml files for the implemented scenary
+ and a file called 'dynamic.suffix' used to complete the dynamic operation
+ in this way:
+
+ dynamic|<initial sequence>|<final sequence>|<dynamic.suffix content>
+
+ For example, you could have this content for 'dynamic.suffix':
+
+ 0|7|CCR-I.xml|CCR-T.xml (0 for timeout means no timeout step)
+
+ in order to generate the operation:
+
+ dynamic|<initial sequence>|<final sequence>|0|7|CCR-I.xml|CCR-T.xml
+
+ which would be parsed for the specific ADML instance programmed:
+
+ dynamic|2000001|2001000|0|7|CCR-I.xml|CCR-T.xml
+
+ The file 'dynamic.suffix' could have several lines for several scenaries.
+ In this case, this script will prompt for the desired one.
+
+ This script will build every operation for the configured ADML instances
+ to complete all the sequence ranges along the whole test system.
+
+
+
+ -s: start testing just after programming, using desired rate: $DESIRED_RATE test cases per second.
+EOF