In order to illustrate the process and fix ideas, let us suppose that it is required to create a TPTP JUnit Test which has (say) the following test methods: testAccount; testOrder; and testInvoice, and we wish the TPTP JUnit Test to operate as follows:
Run testAccount and testOrder in a loop iterated 3 times; then
Run testOrder.
Select the Test Methods tab. Click on the Add button and replace the automatically created 'test 1' method by 'testAccount' (simply edit the Name text box):

Repeat to add testOrder and testInvoice:

To associate test methods with the loop created earlier, switch to the Behavior tab, select the loop, click on the Add... button, and select invocation:
Now select testAccount and testOrder (use <ctrl>click on each) from the Test Invocation dialog:

Click on OK
(Note that tests can be selected from a different suite in the workspace).
TestAccount and testOrder will now be embedded in the loop:

Finally, to include the testInvoice test method, click the Insert... button, select testInvoice, and click on OK:

The behavior process results in TPTP creating Java source which, when run, emulates the specified test behavior. The Java source is given the same name as the TPTP JUnit Test but of type .java (bPUnit.java) and it contains within in it stubs for the testAccount, testOrder, and testInvoice methods. For example, the testAccount method looks like:
public void testaccount()The necessary code for the test should be inserted as indicated.
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.