The TET_EXEC_TOOL configuration variable provides a general-purpose hook which enables you to run test cases under the control of another program; for example: tcc -pe -vTET_EXEC_TOOL=mydebugger -l/tset/area/mybuggytest{1} It is described in the sections entitled "Execute mode processing" and "Configuration variables which modify TETware's operation", both in the TETware Programmers Guide. If your debugger can be invoked from the command line, you can set TET_EXEC_TOOL in the execute mode configuration to the name of your debugger. Additional arguments to the debugger may be assigned to the TET_EXEC_FILE configuration variable.
If you do this, when tcc processes each test case in execute mode it executes the following command: TET_EXEC_TOOL TET_EXEC_FILE test-case-name ic-list This command is executed in the test case execution directory. This method works as described with TETware-Lite. If you are using Distributed TETware it is not possible to interact with test cases and tools ... more.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.