Environment Variables

Testwell CTC++ uses several dedicated environment variables, and some generic ones. They can be setup system wide, user specific or temporarily in the current session as supported by the underlying operating system.

The license server (for floating licenses) or the path to the license file (for evaluation licenses and node-locked licenses) can be stored in one of these variables. LM_LICENSE_FILE is used by all FlexNet-protected tools, TESTWELLD_LICENSE_FILE only by Testwell Tools. Search order is TESTWELLD_LICENSE_FILE first if it has been set.
The data file (MON.dat by default) is written to the directory specified with that variable. It can be used to determine the location at test time.
The name of the data file is determined / overruled with that variable at test time.
On Windows, CTCHOME points to the installation folder of Testwell CTC++. On Linux, this variable must be set to the folder containing the configuration file ctc.ini after installation.
Options for the ctc call can also be set with this variable.
This environment variable is used by the operating system to search for executable files. During installation, the home directory of Testwell CTC++ is added to PATH. Additionally, ctcwrap uses it during a run.
By default, ctc writes intermediate files to the directories for temporary files specified with these variables. With the configuration parameter TMP_DIRECTORY, this location can be overruled.
The user can set this variable to define a list of configuration files (ctc.ini) additionally used. See Hierarchy of Configuration Files and Command Blocks for details.
This environment variable is, despite its name, set and used by the Visual Studio Integration. The user should not change it.
The tool ctcwrap reads this variable to determine the location for ctcwrap-internal, intermediate files. If not set (the standard case), TEMP is used instead.
(deprecated) For symbol and data files, a locking mechanism based on .lock files was used until version 9.0.3. If this variable defining the maximum time to wait is (still) set, also newer versions use that locking mechanism.


To display intermediate commands ctc internally invokes and to keep the temporary instrumented files, you can set CTCOPTS for your current session on Windows with


Setting this environment variable on Linux, you would enter

export "CTCOPTS=-v -k"