Forum Discussion

atul_acrolinx's avatar
atul_acrolinx
Occasional Contributor
5 years ago

TestComplete switching between two windows applications

Hello,   I am currently trying to automate one windows application which has one authentication module in it.    when I launch my windows application, 1. firth thing it asks me is to enter serve...
  • AlexKaras's avatar
    AlexKaras
    5 years ago

    Hi,

     

    NameMapping will certainly work.

    But NameMapping is (just) a more convenient and manageable form of direct process and object referencing. So it is not required to stick to NameMapping/Aliasing (though it is a recommended way) and the following (pseudocode) will work as well:

    var oMyDesktopProcess = Sys.Process(<YourDesktopApp>);

    var oDesktopLogin = oMyDesktopProcess.Window(<LoginWindow>);

    // perform login sequence

     

    var oBrowser = Sys.Browser(<BrowserName>);

    var oPage = oBrowser.Page(...);

    // perform actions in browser

     

    oMyDesktopProcess.Window(<SomeOtherWindow>).Button(<...>).Click();

    oPage.FindChild(...);

    // etc.

    // i.e. no special actions to switch between tested applications are needed with TestComplete

     

Wamboo's avatar
Wamboo
Community Hero
5 years ago

In my opinion, all the operations you mentioned in the entry can be performed by mapping objects to the NameMapping repository.

 

Map the items you are interested in and then work with them in the code.

 

If you want to run some applications other than the one you are working with during the script, add it to TestedApps.

 

The problem of switching between applications will not occur if you have it mapped in the NameMapping repository.

  • atul_acrolinx's avatar
    atul_acrolinx
    Occasional Contributor
    5 years ago

    OK sure, I will try this and get back to you.

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

      Hi,

       

      NameMapping will certainly work.

      But NameMapping is (just) a more convenient and manageable form of direct process and object referencing. So it is not required to stick to NameMapping/Aliasing (though it is a recommended way) and the following (pseudocode) will work as well:

      var oMyDesktopProcess = Sys.Process(<YourDesktopApp>);

      var oDesktopLogin = oMyDesktopProcess.Window(<LoginWindow>);

      // perform login sequence

       

      var oBrowser = Sys.Browser(<BrowserName>);

      var oPage = oBrowser.Page(...);

      // perform actions in browser

       

      oMyDesktopProcess.Window(<SomeOtherWindow>).Button(<...>).Click();

      oPage.FindChild(...);

      // etc.

      // i.e. no special actions to switch between tested applications are needed with TestComplete

       

    • TanyaYatskovska's avatar
      TanyaYatskovska
      SmartBear Alumni (Retired)
      5 years ago

      Hi atul_acrolinx,

       

      Have you managed to resolve the issue? Please share the solution with us.