Offline execution - The test execution batch file

From a TestArchitect client session, you can generate a batch file that invokes the command line tool to perform your tests.

Note:
The following content discusses the batch files that are typically created in the Windows environment, and hence uses commands and other keywords that are specific to Windows. The batch files created under Linux and macOS are, however, quite similar.

Running on a single controller

In Windows, the generated batch file to execute a test only single controller has this form:

:TAExecute0
@echo off
title TestArchitect - Command Line Tool 

ta execute [TACommandLine.jar command line1]
 
exit

The Windows batch commands and keywords in the file are as follows:

Running a test on multiple controllers

The Execute Test dialog box affords you the option to direct your test to be executed on more than a single controller concurrently. When you generate a batch file for multiple controllers, TestArchitect loads it with separate TACommandLine lines which are identical except for the -c ( Machine name or IP address, and port number of the TestArchitect controller that is to run the test) argument.

As an example, the Windows batch file for a three-controller test run might take the following form:

if not "%1" == "" goto :%1
start "TAExecute0" cmd /k "%~dpfx0" TAExecute0
start "TAExecute1" cmd /k "%~dpfx0" TAExecute1
exit

:TAExecute0
@echo off
title TestArchitect - Command Line Tool 

ta execute [TACommandLine.jar command line1]

exit
:TAExecute1
@echo off  
title TestArchitect - Command Line Tool 

ta execute [TACommandLine.jar command line1]

exit

Some of the lines not seen earlier include:

Running a test on multiple mobile devices

As with multiple controllers, you can elect from the Execute Test dialog box to execute a test on multiple devices. The generated batch file looks similar to that of one of the above two cases (depending upon whether one or multiple controllers are involved). For each TACommandLine, an additional argument, -d, is applied, to specify one or more devices attached to the respective controller.

Running multiple test modules

When you specify a serial test run, a separate TACommandLine line is generated for each test module. (One exception, discussed below, is when you specify a test suite and accept the default of running all test module sections and test cases.) In the event that you are also specifying multiple hardware targets (controllers or devices), the number of command lines is multiplied accordingly. For example, we can expand on the above example of executing on three controllers by also specifying two test modules, tm01 and tm02:

:TAExecute0
@echo off 
title TestArchitect - Command Line Tool 
ta execute [TACommandLine.jar command line for tm011]
ta execute [TACommandLine.jar command line for tm021]
exit

:TAExecute1
@echo off
title TestArchitect - Command Line Tool 
ta execute  [TACommandLine.jar command line for tm011]
ta execute  [TACommandLine.jar command line for tm021]
exit

:TAExecute2
@echo off
title TestArchitect - Command Line Tool 
ta execute  [TACommandLine.jar command line for tm011]
ta execute  [TACommandLine.jar command line for tm021]
exit

1 For full details of the TACommandLine structure and its arguments, see Command options.


Copyright © 2024 LogiGear Corporation. All rights reserved. LogiGear is a registered trademark, and Action Based Testing and TestArchitect are trademarks of LogiGear Corporation. All other trademarks contained herein are the property of their respective owners.

LogiGear Corporation

1730 S. Amphlett Blvd. Suite 200, San Mateo, CA 94402

Tel: +1 (650) 572-1400