Forum Discussion

m_essaid's avatar
m_essaid
Valued Contributor
9 years ago

What is the purpose of distributed testing ?

Hi,

 

I have TestComplete and one licence of TestExecute.

 

TestComplete is on my physical computer.

TestExecute is on a VM on the server, running in the night and sometime in the day.

I have one ProjectSuite that contains 6 Projects. Each of them have modular scripts.

 

I see that sometimes TestComplete begins to slow down when TestExecute is running or flushing the logs.

 

Do I need to re-organize my projects ? In the future, I would like to buy another TestComplete licence and run tests simultaneously. How I will manage to do that ?

 

I also have to say that little by little I built a "library" script file that is shared by all Projects. I also share sometimes the mapping (same TestedApps but differents versions).

 

Thanks in advance,

 

Mehdi

  • altemann's avatar
    altemann
    Contributor
    9 years ago

    The purpose of distributed testing is to make sure that the system will keep working even with many users working on the application at the same time. To run tests simultaneously you'll  need to use Network Suite  in your projects. 

     

    You'll probably have to change somethings in your Projects, but if you follow through this tutorial, you should be able to understand how NS works pretty easily: https://support.smartbear.com/articles/testcomplete/distributed-testing-tutorial/ !

     

    :manvery-happy:

     

     

     

     

     

     

    • Colin_McCrae's avatar
      Colin_McCrae
      Community Hero
      9 years ago

      I have a slightly different take on it.

       

      For me, it's more about testing where scenarios require one or two computers/users/applications (delete as applicable) to be involved in a single test.

       

      Or, for where you want to run things remotely in a test lab or such like.

       

      I do performance test work as well and I have yet to hit a scenario where I would use a large volume of TestExecute machines to represent the user swarm. It would be a very expensive way of doing such testing! We often run scenarios with several thousand concurrent users. That would be a BIG chunk of cash required in license fees!

       

      For web based stuff and network driven API's there is plenty of specialist load testing software out there. For desktop stuff, I would most likely use simulated versions/calls rather than multiple full scale installations of the AUT ....

      • tristaanogre's avatar
        tristaanogre
        Esteemed Contributor
        9 years ago

        ...For example, LoadComplete as a load-testing tool? :)

        For "load testing" desktop applications, usually the load is not in the application on the desktop but in the communications to databases, between server and client, etc. These are things that can be profiled using something like AQTime to look for performance problems, memory leaks, etc.

         

        I'm with Colin_McCrae... I wouldn't use Distributed Testing for load testing... it seems to be intended and designed for multi-workstation test scenarios.