cancel
Showing results for 
Search instead for 
Did you mean: 

Disable device cloud extension through automation in test Execute 14.4

SOLVED
Highlighted
Occasional Contributor

Disable device cloud extension through automation in test Execute 14.4

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??

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Occasional Contributor

Re: Disable device cloud extension through automation in test Execute 14.4

I tried different approach. So i have automated the below process using keyword test in Test Complete.

right-click the TestExecute icon in the notification area (tray) and select Install Extensions from the context menu.

Uncheck device cloud.

View solution in original post

11 REPLIES 11
Highlighted
Community Hero

Re: Disable device cloud extension through automation in test Execute 14.4

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

Highlighted
Occasional Contributor

Re: Disable device cloud extension through automation in test Execute 14.4

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
Highlighted
Staff

Re: Disable device cloud extension through automation in test Execute 14.4

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.image.png

Best,
Justin Kim
Highlighted
Occasional Contributor

Re: Disable device cloud extension through automation in test Execute 14.4

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 🙂 

Highlighted
Community Manager

Re: Disable device cloud extension through automation in test Execute 14.4

Thank you Marsha, Justin.

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

 

@BenoitB  @Reshail  @AlexKaras  @cunderw 


Sonya Mihaljova
Community and Education Specialist

Learn SmartBear products in a fun and easy way and prove your knowledge!
>>Participate in the TechCorner Challenge today
Highlighted
Community Hero

Re: Disable device cloud extension through automation in test Execute 14.4

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?

 

Regards,
  /Alex [Community Hero]
____
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.
https://community.smartbear.com/t5/custom/page/page-id/hall-of-fame
================================
Highlighted
Contributor

Re: Disable device cloud extension through automation in test Execute 14.4

@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.

Highlighted
Occasional Contributor

Re: Disable device cloud extension through automation in test Execute 14.4

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

Highlighted
Community Hero

Re: Disable device cloud extension through automation in test Execute 14.4

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.

 

Regards,
  /Alex [Community Hero]
____
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.
https://community.smartbear.com/t5/custom/page/page-id/hall-of-fame
================================
New Here?
Join us and watch the welcome video:
Announcements
Top Kudoed Authors