ConnectToApplication takes lot of time (~1min)

4 posts, 0 answers
  1. p-h
    p-h avatar
    9 posts
    Member since:
    Jul 2018

    Posted 24 Oct 2018 Link to this post

    Repro steps:

     

    1. Start SUT with another automation framework (TestStack.White) in my case

    2. Create an instance of Manager and call ConnectToApplication(int processId)

     

    Expected: The call takes less than 1 sec

    Actual: On one machine it takes less than 1 sec, on the other approx. 1 min

     

    Machine with 1 sec:

    Windows 10 64 bit, TestStudio Trial from online installation

    Machine with 1 min:

    Windows 7 32 bit, TestStudio trial from offline installation..

    Any help would be greatly appreciated.

  2. Elena
    Admin
    Elena avatar
    1104 posts

    Posted 29 Oct 2018 Link to this post

    Hi,

    Thank you for contacting us. 

    As far as I understand you have encountered a delay in starting the process of the application under test when using the Testing Framework - please let me know if I have misunderstood you. 

    I have tried to replicate similar misbehavior on my end but to no avail. Therefore, I would like to ask for some further assistance from your end. Can you please elaborate on the topics below to bring further details about the environment in use: 
    - On the slow Windows 7 machine - when you start the SUT without the Testing framework, do you observe any delay in its start compared to the Windows 10 machine?
    - Is the Win 7 machine a virtual or a physical one? 
    - Is it being used from any other process when you attempt to run the app with the Testing framework test? 

    Additionally, can you please prepare a sample project with a test which demonstrates the code you have implemented to start the application under test? I ask this, as there could be something in the used approach which causes that delay and it will be helpful to examine this as well. 

    Since we do not have any similar observations or such misbehavior reported from other customers, as of my perspective the issue seems to be related to the specific Win 7 machine and how it is configured. So if this is a virtual machine, please let me know if there is any chance you can share this with us so that we can examine itself? 

    I am looking forward to hearing back from you. 

    Regards,
    Elena Tsvetkova
    Progress Telerik
     
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
     
  3. p-h
    p-h avatar
    9 posts
    Member since:
    Jul 2018

    Posted 31 Oct 2018 in reply to Elena Link to this post

    - On the slow Windows 7 machine - when you start the SUT without the Testing framework, do you observe any delay in its start compared to the Windows 10 machine? - No. The app starts normally without any delay. During test it is started by TestStack.White and it takes a few seconds to start. 

    - Is the Win 7 machine a virtual or a physical one? Physical

    - Is it being used from any other process when you attempt to run the app with the Testing framework test? If you consider TestStack.White another process then yes, otherwise no.

     

    Please pay attention that as I mentioned previously there's a difference between the machines:

    the "fast" machine has the following setup: Win10 64 bit, Telerik Test Studio installed from an online installer

    whereas the "slow" machine has the following setup: Win7, Telerik Test Studio installed from an offline installer because it's forbidden to put it online.

    Can this difference account for the described behaviour?

     

    Thanks in advance.

  4. Elena
    Admin
    Elena avatar
    1104 posts

    Posted 05 Nov 2018 Link to this post

    Hello,

    Thank you for the additional notes. 

    Let me please address first your concerns about the installation you have performed on the two different machines - the installation itself actually does not require internet connection. Having that said, the issue might be related to the OS and its specifics, but not to how the Telerik Testing Framework was installed. 

    To get back to the issue I would like to share what I understood so far - it seems your testing solution is based on a testing framework called TestStack.White. As we are not very familiar with it, can you please share some additional details how the Telerik Testing Framework is implemented in that solution? Thank you for that in advance.

    Additionally, based on the shared so far details, it will be difficult for us to investigate what could be causing the performance problem on your side. Given this, it will help us a lot if we can further examine the faulty behavior on our side. This will allow us to troubleshoot and debug the concrete problem and hopefully find the best suitable solution for it. This said, will it be possible to provide us the automation project for further examine? That way we could better understand how the Telerik Testing Framework is being used and if there is any possible way to improve the implementation or provide guidance on it.

    Thank you for your help and cooperation in advance. I am looking forward to your reply.

    Regards,
    Elena Tsvetkova
    Progress Telerik
     
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
     
Back to Top