Forum Discussion

David91's avatar
David91
Frequent Contributor
8 years ago

Other work during the running test

Hi, it's during the test to perform another job in another program on the same PC where you run the test?

Thank you

  • John_Laird's avatar
    John_Laird
    8 years ago

    A practical work around...

    1. Install TC12 on one VM (called 'devVM') and TE12 on another VM (called 'runtimeVM'). Put your licensing software on a physical machine that both VMs can reach.

    2. Set up a remote GIT repository on yet another VM.

    3. Install the Tortuous GIT plugin on 'devVM' and 'runtimeVM' with local repositories on each.

    4. Develop your tests on 'devVM'. When you are at a stopping point, commit your changes locally. When you are finished with a test, push your change to the remote repository.

    5. Go to 'runtimeVM' and pull from the remote repository. Verify that you can kick off the test via Test Execute and that it works as desired. Test Execute can be kicked off automatically by some scheduled batch file or by an automated build system while you develop additional tests in parallel on 'devVM'.

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    8 years ago

    Short answer: no.

    Longer answer: TestComplete uses hooks into the keyboard and mouse of the operating system to perform clicks and keystrokes against your application, especially for functional test using the UI.  Any actions by you on the machine while the test is running will interfere with this.  Even if you are not running tests against the UI, you could impact performance, other services, etc., that may be accessed by the tests thus invalidating the tests themselves. It is generally good practice, not just for TestComplete but for test automation in general that, if you need to use your workstation while tests are running, then you should invest in another machine, whether physical or virtual, on which to execute the tests. For SmartBear products, this means using either another license of TestComplete or, optimally, a license of TestExecute.

    • baxatob's avatar
      baxatob
      Community Hero
      8 years ago

      Yeah, it will look like two people work on one PC.

  • John_Laird's avatar
    John_Laird
    Contributor
    8 years ago

    A practical work around...

    1. Install TC12 on one VM (called 'devVM') and TE12 on another VM (called 'runtimeVM'). Put your licensing software on a physical machine that both VMs can reach.

    2. Set up a remote GIT repository on yet another VM.

    3. Install the Tortuous GIT plugin on 'devVM' and 'runtimeVM' with local repositories on each.

    4. Develop your tests on 'devVM'. When you are at a stopping point, commit your changes locally. When you are finished with a test, push your change to the remote repository.

    5. Go to 'runtimeVM' and pull from the remote repository. Verify that you can kick off the test via Test Execute and that it works as desired. Test Execute can be kicked off automatically by some scheduled batch file or by an automated build system while you develop additional tests in parallel on 'devVM'.

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      8 years ago

      Yup!  Exactly.  If you want to parallel develop your tests (or do any other work, actually) you need to set up an environment for development and one for execution.

       

      I use Mercurial, personally, with the Tortoise UI for my own work.  Same basic deal. :)