Manfred_F
Regular Contributor
Joined 11 years ago
User Profile
User Widgets
Contributions
Re: Object sometimes doesn't support Exists
Hi, my impressionis, that problem with .exists property happen for alias objects, whereas controls sometimes have problems with .Child, .ChildCount, .MappedName, .Parent properties: I get a vb runtime error in this case. As saíd before, when I read .Fullname before, no error shows up. I hope you understand that I can not invest much more time into this case, as it took me 3 weeks to fix this mess, and I should have done other work in this time.. Regards, Manfred1.7KViews0likes3CommentsRe: Object sometimes doesn't support Exists
Yes, I work with the desktop application. The references are obtained as follows: 1) use alias to access the dialog 2) use child, children etc to step down the hierarchy. The effect showed up from within script extensions and from native vb code also. The effect reproducibly occurred at specific locations in my scripts and did not occur at many others. I'm quite sure that it is not a timing issue. Regards, Manfred1.7KViews0likes5CommentsObject sometimes doesn't support Exists
had similar problems as described in https://community.smartbear.com/t5/TestComplete-Desktop-Testing/Object-sometimes-doesn-t-support-Exists/td-p/183729/page/2 In my case, not only the .Exists property of alias objects was affected, but also .Exists, .Child, .ChildCount, .MappedName, .Parent properties of normal controls. I use alias objects only to identify dialogs, then navigate down the hierarchy.. The workaround is to access the control's .FullName property before accessing anything else. So: for alias objects, call .refreshMappingInfo(), for controls get .FullName. I'm still using TC11.30..Solved1.8KViews0likes8CommentsRe: Namemapping nightmare
One approach is to build and use Your own framework to access Your app's objects. I only use name mapping and aliases for basic addressing - of the dialogs, but not for the hundreds and hundreds of fields thereon. So, in Your framework, provide a dialog object and make use of an alias to access it. For the child controls, use Your own Control objects and for their addressing Your own addressing methods. If data or functions are scattered to some technical ui objects, You can hide this inside Your control object. This is some work to do, but it gives You a stable and maintainable result.1.7KViews0likes2CommentsRe: How to close Excel window cleanly
hi, my Excel-closing routine works as follows: While Excel Process exists get visible "XLMAIN" Windows If #XLMAIN > 0 Then Set ExcelApp = Xlmainwindow.Window("XLDESK").Window("EXCEL7").NativeObject.Application.Application For Ix = ExcelApp.Workbooks.Count To 1 Step -1 ' close Workbooks without saving If ExcelApp.Workbooks(Ix).Windows(1).Visible Then ExcelApp.Workbooks(Ix).Close False Next ExcelApp.Quit Set ExcelApp = Nothing End IF End While1.9KViews0likes0CommentsRe: TestComplete/TestExecute Drop-downs
the issue is to determine, when Your app is really ready for input. This can be complicated. I've got the same type of issue and solved it by observing the cursor type (changing from wait to normal and back several times) and additionally wait a little. Of course, this can be solved by waiting a sufficient long time, but what would be sufficient? Can Your user somehow recognize, that the app is ready for input? Then You could use the same criterion for automation.. Regards, Manfred1.6KViews1like2Comments