Forum Discussion

delito's avatar
delito
Occasional Contributor
4 years ago
Solved

Chrome Login popup not detected

TestComplete

Version: 15.31.374.7 x64

Browser: Chrome Version 99.0.4844.51 (Official Build) (64-bit)

Running: Locally

 

Issue:

I've been using the below piece of code for 6+ months and occasionally it fails and will not identify the login fields to populate the username and password, is there a better more reliable way to handle this ?

 

 

 

 

 

 

 

 

        if(page.WaitLogin(3000).Exists)
        {
          Aliases.browser.pageSignOut2.Login.UserName = Project.Variables.Username;
          Aliases.browser.pageSignOut2.Login.Password = Project.Variables.Password;
          Aliases.browser.pageSignOut2.Login.buttonOk.Click()  
       }

 

 

 

 

 

 

Ive also tried the below which has occasionally worked but at the moment its not.

 

 

 

 

 

      if(page.WaitLogin(3000).Exists)
        {
//          Aliases.browser.pageSignOut2.Login.textboxUsername.Keys(Project.Variables.Username);
//          Aliases.browser.pageSignOut2.Login.textboxPassword.Keys(Project.Variables.Password);
//          Aliases.browser.pageSignOut2.Login.buttonOk.Click()
         
       }

 

 

 

 

 

 

Debugging
Object Recognition
script tests
web testing
  • MisterB's avatar
    MisterB
    5 years ago

    Hi Johan,

     

    After producing the report, you can copy the URL and share that.  Each time the URL is loaded, it will dynamically update the report from the source data.

     

    Another tip that might help is within the report URL, you should see the key of the criteria that you are using, e.g. Test Cycle.  You can manually change that part of the URL for another Test Cycle Key to run the same report on another cycle of your choice.  This works in many parts of the system and is also useful for navigating between issues or test cases for example.

     

    Regards, Andy