I ran our application using keyword testing and found out an error in my log message which says: 'Authentication form' window is invisible and cannot be activated.
Any idea what would have cause this error??
Also one interesting thing is I have to repeat our application without closing them, so the first time no error message seen on Authentication window but it is the second time above error message logged .
This error is, basically, exactly what it says. The window can't be accessed. It's not there.
If you're seeing the window on screen then here's another possibility I've run into in the past. It's possible that the application is spawning multiple instances of the same window. So when you go through it the first time it's fine, but when you go through it the second time, it's finding the first instance of that window which is now set to be invisible.
I've reported these issues as bugs in the past. Some get fixed, others are issues inherent in the development language which they are simply not able to or unwilling to resolve. In these cases you can do something like create a function will will create an array of controls matching your criteria (using the FindAllChildren method for instance) and then go through each array item and check that the Visible property is True before returning it as object to interact with.
Try using the LogAppStructure function we gave you in another thread (http://www.sqaforums.com/showflat.ph...gonew=1#UNREAD) to find out whether the window you need is visible and exists when you are trying to work with it. It can happen that you actually need to work with another window which has similar properties due to the windows destruction/creation problems mentioned by Brent. If you fail to find the cause of the problem by using the test log, please zip your entire project suite folder along with the log of the failed test execution and send us the archive via our Contact Support form (http://www.automatedqa.com/support/message). Make sure that messages in your log correspond to the latest version of your tests (and that the log contains LogAppStructure results).