Forum Discussion

kenhepworth's avatar
kenhepworth
Occasional Contributor
13 years ago

The window is invisible and thus cannot be activated

Hi,



I currently have the situation where I am attempting to execute some tests within the application where it enters some details for users of the application, so therefore it needs to enter some passwords into the details. But for some reason when I attempt to execute the entry of the passwords, it states that 'The window is invisible and thus cannot be activated'. This is quite concerning because it is only just before this that I attempt click on the window on the line to enter the password. On the same window in the same sort of controls I successfully enter the name and user id of the user whose details I am entering. So what puzzles me is why it can see some and not these two.



I am attempting to do this with a keyword test, as idenified in attachment 1, and the two lines of code where I am getting an error are highlighted.



In attachment two is the application window that I am testing, and I have highlighted the two fields that I am enterering data.



Any suggestions would be great thanks.



Regards,

Ken 

3 Replies

  • kenhepworth's avatar
    kenhepworth
    Occasional Contributor
    Hi,



    No one has any advice on why his might be happening?



    Regards,

    Ken
  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    Without some greater details of the specifics of the component, all I can offer is a guess.



    My guess is that the Alias/Mapping of those password fields may not necessarily be the same component visible on screen and so the keyword test attempt to interact with them may be getting misdirected.  I'd suggest using the Object Spy and see what you can find out about those components and make sure that there's not two layers there of some sort that is causing something like this.
  • SIStester's avatar
    SIStester
    Occasional Contributor
    I had the same problem last week. There's a webinar you can watch that explains Name mapping in details and how to debug those errors, here's the link.



    the problem is that your two textboxes have the same name, so you have to make them out by something else than the name (the index is nice, or you could seperate them by their tag.. just try finding what's different between the two, and if you're still in developement phase, you could ask your devs to give them a different name)



    follow the link on your test complete start page to see recorded webinars