User Guide Test execution Working on multiple test harnesses

 Configuring harness pool size

Configuring harness pool size

TestArchitect allows you to determine the maximum allowable number of harnesses (harness pool size) running on a TestArchitect controller at a time.

Running multiple harnesses is a memory-consuming task. So if you change the harness pool size, you had better to change the heap size allocated to the TestArchitect Controller and an individual harness through the -Xmx and -Xms parameters accordingly:

Changing the harness pool size

In the event that the number of running harnesses has reached the maximum allowable number of harnesses but you are still invoking the execution of more harnesses, the TestArchitect Controller will not run the new harnesses instantaneously. Instead, the TestArchitect Controller will put these harnesses into a queue.

For example, you try to run 12 harnesses in parallel although the maximum allowable number of harnesses is only 10. The 10 harnesses sent to the TestArchitect Controller first start to run, whereas the 2 remaining ones - temporarily called the 11th and 12th harnesses - are pending. When one of the 10 harnesses completes, the 11th harnesses starts to run. It is not until one more harness completes, the 12th harness starts to run.

• The harness pool size is 8 by default.
• However, you can adjust the harness pool size as long as the CPU and memory of your machine can handle it and resource consumption of AUT does not exceed the available amount. Once you change the harness pool size, do not forget to change the heap size of the Test Controllerand an individual harness.

To define the maximum allowable number of harnesses, follow the instructions below:

1. Browse to the following folder:

   • In Windows: %SystemDrive%\Users\Public\LogiGear\TestArchitect\controller
   • In Linux: /usr/local/logigear/testarchitect/controller.

2. Open the abt.ini file in a text editor; Notepad++ is recommended.

3. Find the line that begins with number pool harnesses and change its value to the desired number.

   Notes: 
   The value must be a positive integer. So long as you set an invalid value (negative number or zero), the default value will be used.
   
   

4. Save the abt.ini file.

Changing the heap size of the TestArchitect Controller

The Java heap is the memory portion where blocks of memory are allocated to objects and freed during garbage collection.

• -Xmx: sets the maximum Java heap size. (Learn more)
• -Xms: sets the minimum Java heap size.

The TestArchitect Controller is used to execute all harnesses. Thus if you raise the harness pool size, it is necessary to increase the heap size of the TestArchitect Controller.

Follow the instructions below to change JVM parameters:

1. Browse to the following folder:

   • In Windows: %SystemDrive%\Users\Public\LogiGear\TestArchitect\controller
   • In Linux: /usr/local/logigear/testarchitect/controller.

2. Open the abt.ini file in a text editor; Notepad++ is recommended.

3. Under JAVA OPTIONS, insert/edit the Xmx or/and Xms parameters.
   
   

4. Save the abt.ini file.

Changing the heap size of an individual harness

Generally speaking, the heap size of an individual harness is inversely proportional to the harness pool size simply because your machine’s memory is a fixed amount. If you raise the number of harnesses running in parallel, decrease the heap size.

Perform the steps below to adjust the -Xmx and -Xms parameters:

1. Browse to the following folder:

   • In Windows: %SystemDrive%\Users\Public\LogiGear\TestArchitect\Automation.
   • In Linux: /usr/local/logigear/testarchitect/automation.

2. Open the automation.ini file in a text editor; Notepad++ is recommended.

3. Under the JVM section, insert/edit the -Xmx or/and -Xms parameters.
   
   

4. Save the automation.ini file.

Related tasks

Running multiple harnesses from TestArchitect Client

Creating a batch file to run multiple harnesses