Run/Debug Configuration: Boost.Test
Use this page to configure run/debug options for Boost.Test - a C++ testing framework.
Click here for the description of the options that are common for all run/debug configurations.
Choose Suite/Test to run a specific suite and its tests. Choose Pattern to run a combination of different suites and tests.
These text boxes are displayed if Suite/Test is selected. Here you need to specify a suite and its tests to be run.
This text box is displayed if Pattern is selected. Here you need to specify a combination of suites and tests to be run.
|In this text box, type a list of arguments to be passed to the program in the format you would use in the command line. If necessary, click the button and type the desired arguments in the Program Parameters dialog box. |
Use the same rules as for specifying the VM options.
|In this text box, specify the current directory to be used by the running application. This directory is the starting point for all relative input and output paths. By default, the field contains the directory where the project file resides. To specify another directory, click the Browse button select the directory in the dialog that opens. |
Click the icon to view the list of available path variables that you can use as a path to your working directory.
|Click Browse to open the Environment Variables dialog box, where you can create variables and specify their values. |
Note that you can copy-paste the contents of the Environment variables field without having to open the Environment Variables dialog box.
Shorten command line
| Select a method that will be used to shorten the command line if the classpath gets too long or you have many VM arguments that exceed your OS command line length limitation: |
Click this button to add a new configuration to the list.
Click this button to remove the selected configuration from the list.
Click this button to create a copy of the selected configuration.
Click this button to edit the default configuration templates. The defaults are used for newly created configurations.
N/A or N/A
|Use these buttons to move the selected configuration or folder up and down in the list. |
The order of configurations or folders in the list defines the order in which configurations appear in the Run/Debug drop-down list on the main toolbar.
Move into new folder / Create new folder
|Use this button to create a new folder. |
If one or more run/debug configurations are in focus, the selected run/debug configurations are automatically moved to the newly created folder. If only a category is in focus, an empty folder is created.
Move run/debug configurations to a folder using drag-and-drop, or the buttons.
Click this button to sort configurations in alphabetical order.
In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.
This node in the left-hand pane of the dialog box contains the default run/debug configuration settings. Select the desired configuration to change its default settings in the right-hand pane. The defaults are applied to all newly created run/debug configurations.
| Select this check box to make the run/debug configuration available to other team members. |
The shared run/debug configurations are kept in separate xml files under
This check box is not available when editing the run/debug configuration defaults.
Single instance only
|If this check box is selected, this run/debug configuration cannot be launched more than once. |
Every time a new run/debug configuration is launched, AppCode checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place.
This makes sense when the usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources.
If this check box is not selected, it is possible to launch as many instances of the runner as required. So doing, each runner will start in its own tab of the Run tool window.
|Specify which tasks must be performed before applying the run/debug configuration. The specified tasks are performed in the order they appear in the list. |