Forum Discussion
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.
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 🙂
- AlexKaras4 years agoChampion Level 3
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?
- Saman_Akhtar4 years agoOccasional Contributor
Yes I am restarting test execute for running either single test or groups of test.
- AlexKaras4 years agoChampion Level 3
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.