Disable device cloud extension through automation in test Execute 14.4

[Saman_Akhtar]

During test execution using TestExecute, I am getting device cloud pop up. I know how to disable it by following steps.

To disable a plugin

1. Right-click the TestExecute icon in the notification area (tray) and select Install Extensions from the menu. This will call the Extensions dialog.

2. In the dialog, clear the check box next to the plugins you want to disable and click OK.

But my requirement is to disable silently or through automation.

Note: we can update registry key due to access

Any suggestion??

[Marsha_R]

Scroll down to the bottom of this page and there are instructions for uninstalling a plug in from the command line.

https://support.smartbear.com/testcomplete/docs/working-with/extending/installing.html

[Saman_Akhtar]

Similar uninstalling option is there for Test Execute. But i am unaware of plugin name for device cloud. Is it possible to specify its exact name?

1 Also any mds or any Test Execute file which if we modify can remove device cloud plugin?

2 Or any way to obtain TestExecute object so that we can go Install Extension -> Disable checkbox next to Device Cloud?

FYI : Plugins location in registry key location is:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SmartBear\TestExecute\14.0\UserData\managers\{69fb0002-d3da-41ed-909b-12bef03232b8}\plugins

[hkim5]

I'm not sure if I'm understanding this correctly, but are you trying to select and unselect different modules during automated test runs? Are using additional command line arguments an option for you? If so, I'd suggest looking at the /EnableModule argument, which can be used to specify precisely which TestComplete modules to enable during test execution.

[Saman_Akhtar]

Thank you for reply. 

Yes I am trying to unselect  only device cloud module. I had read the same document as you mentioned.

I even tried this \EnableMode parameter with TestExecute and I am able to achieve the desired result.

But unfortunately not going to opt for this option.

The reason is I need to run 1000+ test cases and for each run i need to use \EnableMode.

I already have other parameters to TestExecute.  Because of \EnableMode. its slowing down launching of test execute. I don't want to effect the performance of running of 1000+ test cases.

Hence needed any alternative to this solution.

But thank you for patiently replying to my query 🙂 

[sonya_m]

Thank you Marsha, Justin.

Let's see if anyone has more ideas on this one!

@BenoitB  @Reshail  @AlexKaras  @cunderw 

[AlexKaras]

Hi,

> I don't want to effect the performance of running of 1000+ test cases.

Does this mean that you are restarting TestExecute for every test? How your tests are organized?

[Reshail]

@Saman_Akhtar ,

I think those are your best options. But you could try editing the registry value (since you've already figured out the path for it) through command line and execute that before starting your execution. 

https://superuser.com/questions/607572/how-do-i-modify-the-data-of-an-existing-registry-key-value-na...

2.Or any way to obtain TestExecute object so that we can go Install Extension -> Disable checkbox next to Device Cloud? 

I dont think that will be possible since test execute has not launched yet.

[Saman_Akhtar]

Yes I am restarting test execute for running either single test or groups of test.

[AlexKaras]

Hi,

> Yes I am restarting test execute for running either single test or groups of test.

Any real reason for this? Why not to organize your tests using Test Items tree and execute this or that branch or the whole tree as required?

Restart of TestExecute (like restart of any application) is expensive in terms of performance and I would not follow this way.