You are here: TETworks > TETware FAQ Index > FAQ
The TETware Issue 1 Design specification was completed 30 April 1996 and is available at http://tetworks.xopen.org/tet3spec.html.
The internal workings of the TETware tcc are completely different from the tcc supplied with earlier TET versions.
One of the motivations of this change was to enable the functionality provided by dTET2 and ETET to be integrated in a single product. Another was to make it easy to add new directives and other functionality to TETware, and to port it to other environments.
M5. A requirement we have is to be able to run our tests repeatedly for hardware stress testing. How can we do this?
A requirement of our manufacturing people is for tcc to be able to invoke repeated executions (eg for hardware stress testing) without having to change the scenario files. Developers write the scenarios and dont want repetitive execution. But manufacturing, who wish to reuse the tests, do.
There are a couple of ways that you can do this using existing TETware functionality.
Method (1) - if you know how many times the manufacturing people want to repeat when you write the scenario.
You can provide more than one scenario when you write the scenario file.
One scenario can list all the tests, and the other can repeat the first the required number of times. For example:
Your developers can use the scenario called "developer" in the example above and the manufacturing people can use the scenario called "manufacturer".
You can choose which scenario to execute on the tcc command-line. For example, to execute all the tests in the list once:
or to execute all the tests in the list 100 times:
Method (2) - if you want to specify the number of times to repeat the scenario on the tcc command-line.
In this method, you specify the basic scenario in a file and add a :repeat: directive on the command-line.
The scenario file should contain the non-repeating list of tests as in Method (1); for example:
To execute all the tests once, you invoke tcc in the same way as in Method (1); for example:
You can specify both the -l and -s options to process a scenario defined in a file under the control of a directive specified on the command-line. So, to repeat all the tests 50 times, you would say:
or, to repeat all the tests for (at least) 10 hours, you would say:
Not directly, however in conjunction with The Open Group's Assertion Definition Language (ADL) tool this is possible. See http://adl.opengroup.org for more information.