Within the Overview tab view, if the Implement Test Behavior as code check box is checked (as in the example above) then the Behavior is purely code-based i.e. the test methods will be executed exactly as presented in the Test Methods view. This is the position with respect to TPTP JUnit tests that have been created as a result of importing JUnit tests into a TPTP JUnit test.
If the Implement Test Behavior as code check box is cleared then an additional tab Behavior becomes available (note that the behavior feature should be used only for TPTP JUnit Tests which have been created manually):

The behavior tab allows you to specify the frequency and order in which test methods are run. This is done via invocations and loops: invocations allow you to specify which test methods you wish to run, and in which order; loops allow you to embed the chosen test methods within a loop which can be iterated one or more times. Behaviors can contain a mixture of invocations and loops. To set up a single loop:
Select the Behavior tab, click on the Add... button and select Loop:

This will setup a behavior under the control of a single loop. We shall add the test methods to this loop shortly.
By default, the number of iterations of a loop is 1. This can be changed via the Number of Iterations box which specifies the number of loop iterations:

If Synchronous is checked and more than one iteration is specified, the loop iterations execute sequentially. If Synchronous is unchecked and more than one iteration specified, the loop iterations execute concurrently.
The Up and Down buttons are used to alter the relative positions of invocations and loops. The Add and Remove buttons are used to add/remove selected loops/invocations.
Loops can be nested, and invocations can exist outside of a loop.
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.