- echo "Remember that you could start traffic using:"
- echo " ./operation.sh \"test|ttps|<test cases per second rate>\""
- echo
- echo "For example, to reach $DESIRED_RATE test cases per second:"
- echo " ./operation.sh \"test|ttps|$RATE_PER_INSTANCE\""
+ cat << EOF
+
+To start testing, you must use the './operation.sh' script. Use '-h'
+ to get detailed help. The most common commands used for testing are:
+
+ * Enable reports dump for failed tests:
+ ./operation.sh "test|report|failed"
+
+ * Launch traffic:
+ ./operation.sh "test|ttps|<test cases per second and instance(*)>"
+
+ (*) note: ttps value is related to a single instance: you should"
+ divide the desired CPS by the number of instances. For"
+ exampl, if you need $DESIRED_RATE test cases per second:
+
+ ./operation.sh "test|ttps|$RATE_PER_INSTANCE"
+
+ * Stop traffic:
+ ./operation.sh "test|ttps|0"
+
+ * Reset already classified (Success/Failed) test cases:
+ ./operation.sh "test|reset[|soft]"
+
+ * Reset also 'in-progress' state test cases:
+ ./operation.sh "test|reset|hard"
+
+Remember that './operation.sh' broadcasts the operation scripts along
+ the ADML instances, then some operations should better be used within
+ a specific 'ADMLS/ADML-<instance>' directory to avoid console spam,
+ for example:
+
+ * Check a testcase in runtime:
+ ADMLS/ADML-001/operation.sh "test|look|<test id>"
+
+ * Execute the next programmed test case:
+ ADMLS/ADML-001/operation.sh "test|next"
+
+ * Interactive-step execution:
+ ADMLS/ADML-001/operation.sh "test|interact|<steps to execute>|<test id>"
+
+ * Summary:
+ ADMLS/ADML-001/operation.sh "test|summary"
+
+EOF
+