Forum Discussion
hlalumiere
12 years agoRegular Contributor
In addition to the previous answers, most if not all controls for .NET that are not directly supported in TestComplete are easily addressable through MSAA. If you run across something that just doesn't look right in TestComplete, try adding the class (WndClass property value of the object) to the list of MSAA-handled classes in the MSAA options on the project property page.
As for integrated web browsers, the .Net WebBrowser control has a tendency to do weird things when plugins are involved from my experience. You can try setting the WebBrowser object's .RegisterAsBrowser property to True in the application, I have seen this do a difference in the past in some cases.
As for integrated web browsers, the .Net WebBrowser control has a tendency to do weird things when plugins are involved from my experience. You can try setting the WebBrowser object's .RegisterAsBrowser property to True in the application, I have seen this do a difference in the past in some cases.
Related Content
Recent Discussions
- 12 hours ago