In the same fashion that we can use the GUI to enable/disable extensions, it would be nice to be able to choose which extensions are active when TestComplete starts up.
/EnableExtension:[AllCo...
Isn't this already available?
-
/install:extension_name (or /ip:extension_name) - Installs the specified TestComplete plugin and enables it on the product start. The extension_name parameter specifies the fully-qualified name of the desired plugin file (.pls). This command may help you customize a testing environment on remote computers according your needs.
Notes:
-
If the name of the plugin file includes spaces, it must be enclosed in double quotes:
"TestComplete.exe" /install:"C:\TestComplete plugins\plugin.pls" -
You can install only one plugin at a time.
-
When you use the command line to load a project, the specified plugin will be installed before the project is opened.
-
You cannot use this command-line argument to install script extensions.
-
-
/uninstall:extension_name (or /up:extension_name) - Uninstalls the specified TestComplete plugin on the product start. The extension_name parameter specifies the fully-qualified name of the plugin file (.pls). This command may help you customize a testing environment on remote computers according your needs.
Notes:
-
If the name of the plugin file includes spaces, it must be enclosed in double quotes:
"TestComplete.exe" /uninstall:"C:\TestComplete plugins\plugin.pls" -
You can uninstall only one plugin at a time.
-
This command will not delete the actual file from the disk.
-
When you use the command line to load a project, the specified plugin will be uninstalled before the project is opened.
-
You cannot use this command-line argument to uninstall script extensions.
-