Forum Discussion

obaid_shirwani's avatar
obaid_shirwani
Contributor
5 years ago

Unable to access (Verify/Execute) a VM for parallel testing

Hi,   I am facing a situation where am not able to decide, where the problem lies. Consider the following situation:   1. Happy Case: I am able to access a VM machine and execute test cases on it...
  • AlexKaras's avatar
    AlexKaras
    5 years ago

    Hi,

     

    > Is there a way, TestComplete may develop a feature to solve such hurdles?

    I am not employed by SmartBear and cannot speak for them. If you like you may ask Support directly via the https://support.smartbear.com/message/?prod=TestComplete form.

    My personal opinion is that this is nearly to impossible. Just because this is the built-in OS security/legal feature.

    Depending on the level of permissions that you have for your test machines, you may consider, for example, to keep machines in not-locked state (if this is possible).

    Another possible approach (which requires local administrative permissions for the test machines) is to create a scheduled task that triggers on OS start. The task should delete registry entries that trigger display of the Legal Notice window. (I don't have relevant registry path at hand as we speak but you may either Google it or let me know and I will post it here.)

     

obaid_shirwani's avatar
obaid_shirwani
Contributor

Hey Alex,

 

Sorry for the late reply. I have filed an RFC. The security team will consider removing the Welcome Banner for a day (24 hours max). But, the company policy wont let us remove that banner for ever. If this fixes the issue (and now i am sure its the pain point) we still wont be able to use this in long terms.

 

Is there a way, TestComplete may develop a feature to solve such hurdles?

 

Best regards,

 

Obaid Shirwani

AlexKaras's avatar
AlexKaras
Champion Level 3
5 years ago

Hi,

 

> Is there a way, TestComplete may develop a feature to solve such hurdles?

I am not employed by SmartBear and cannot speak for them. If you like you may ask Support directly via the https://support.smartbear.com/message/?prod=TestComplete form.

My personal opinion is that this is nearly to impossible. Just because this is the built-in OS security/legal feature.

Depending on the level of permissions that you have for your test machines, you may consider, for example, to keep machines in not-locked state (if this is possible).

Another possible approach (which requires local administrative permissions for the test machines) is to create a scheduled task that triggers on OS start. The task should delete registry entries that trigger display of the Legal Notice window. (I don't have relevant registry path at hand as we speak but you may either Google it or let me know and I will post it here.)

 

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    5 years ago

    Because the VMs are "locked in a closet" (basically, no one can get to them to do anything), we have ourse set up that they are always unlocked.  This is a group policy that we apply to ONLY those machines and our security team is fine with (regulated health-care industry).  This, I believe, is going to be your best solution.

    • obaid_shirwani's avatar
      obaid_shirwani
      Contributor
      5 years ago

      We cannot remove the policy pushed by Global Server Ops team or Network Security team. Its strictly against the policies. There has to be some other way out as data is extremely critical and no security breach is tolerated. 

  • obaid_shirwani's avatar
    obaid_shirwani
    Contributor
    5 years ago

    Alex,

     

    Thanks for all your time on this.

    1. The issue is, our organization has very strict policies regarding servers and client data. The security team has approved only a 24 hours slot for the removal of this 'Warning Banner' so that we can verify the postulate, that this is the only hurdle which is keeping TestComplete from performing the job. So, it might not be possble for us to carry out parallel executions on VM.

     

    2. What i had on mind was:

    a. Create multiple VMs on cloud.

    b. Setup 'TestExecute' on each VM.

    c. Whenever required, fetch the latest code from repo on the VM machine.

    d. Start the VM and perform auto-logon whenever a test execution is needed.

    e. Shutdown the VM when job is done and logs are uploaded.

     

    But this Security Warning Banner will block it. Am afraid that we will have to look for other options :(

     

    Thanks again for all your time and help. Ill update you in case any progress is made.

     

    Best regards

    • AlexKaras's avatar
      AlexKaras
      Champion Level 3
      5 years ago

      Hi,

       

      > But this Security Warning Banner will block it. Am afraid that we will have to look for other options

      Yes, Legal Notice well might be a road-block.

      I just thought about one idea, in case suggestion from Robert is not acceptable as well. (To keep VM up, running and not locked.)

      If I remember it right, Legal Notice is displayed after login/password credentials were entered and accepted.

      The idea is to configure VM to auto-logon and create some scheduled task triggered on user's logon (or on OS start with some delay to let OS start, preform auto-logon and display Legal Notice). Then the task should try to focus the OK button and press it by blindly sending Tab, Space and Enter keypresses. If you are lucky, this will dismiss of the Legal Notice window. Otherwise, I am afraid that you will have to manually start and log in into every VM and then start (automated) test code deployment and tests execution.

       

      • obaid_shirwani's avatar
        obaid_shirwani
        Contributor
        5 years ago

        Unfortunately not so. The Banner is displaed as soon as any machine on our network boots up. You first get to accept the policies mentioned on the Banner by pressing that OK button. Once that is pressed, you get the Credentials screen.