Contributions
Object Browser displays nonsensical descriptions of Objects
I've found that I can't run any TC tests on my machine. The reason is because TestComplete is displaying incorrect nonsensical information regarding any of my processes. For example, whereas all our scripts have the correct object displayed, such as: Set w2 = w1.WinFormsObject("tbdIncidentDetails") Call w2.ClickTab("Incident") Set w3 = w2.tbdIncidentDetails_TabPage0.fraIncidentDetailsTab0 Call w3.WinFormsObject("cboCategory").Keys(sCategory) Call w3.WinFormsObject("cboCategory").ClickItem(sCategory) Our new scripts are being created with nonsesical Object Names, for example: Call w.Window("WindowsForms10.Window.20808.app.0.378734a").Click(83, 122) Set w = w2.Window("WindowsForms10.Window.8.app.0.378734a", "Incident Search ") Set w3 = w.Window("WindowsForms10.SysTabControl32.app.0.378734a") Call w3.ClickTab("Incident Details") Set w4 = w3.Window("WindowsForms10.Window.8.app.0.378734a", "Incident Details").Window("WindowsForms10.Window.8.app.0.378734a").Window("WindowsForms10.EDIT.app.0.378734a", "", 3) Call w4.Click(28, 13) w4.wText = "2131441" Call w4.Keys("[Enter]") w.Window("WindowsForms10.BUTTON.app.0.378734a", "&Details").ClickButton Set w3 = w2.Window("WindowsForms10.Window.8.app.0.378734a", "Incident Details") Set w2 = w3.Window("WindowsForms10.Window.8.app.0.378734a", "", 2).Window("WindowsForms10.Window.8.app.0.378734a") In other words, all the correct Object descriptions (from the Object Browser), such as "w1.WinFormsObject("tbdIncidentDetails")" are now being recorded with the gibberish Object Names, such as "w.Window("WindowsForms10.SysTabControl32.app.0.378734a")" Has anyone else seen this behaviour? It only appears to occur on some machines, and not others. As it stands, all our current scripts won't run on any machine where this is occurring, as our scripts are trying to hook onto the "correct" Object Names. Thanks.15KViews0likes1CommentName Mapping producing nonsense WndClass and MappedName values
Hi, We've been using TestComplete for a number of years. But since version 7, we've been having a problem with the NameMapping function. For some reason TestComplete reads the FullName value in our vb.net WinForms application incorrectly. When we recorded the scripts we got, for example: Set irsfr01648 = mdiClient.IRSFR01648 But recently, this same action is recording as: Set irsfr01648 = pulse.wndWindowsForms10Window8app0378734a4.WindowsForms10MDICLIENTapp0378734a.wndWindowsForms10Window8app0378734a Also, in the object browser, the FullName is sometimes: Sys.Process("PULSE").WinFormsObject("PULSEMdi").WinFormsObject("MdiClient", "").WinFormsObject("IRSFR01648") And the WndClass value is: WindowsForms10.Window.8.app.0.378734a Whereas other times the WndClassvalueis mdiClient.IRSFR01648 - this is the correct value. For this reason, in most cases our newer scripts fail to run because of the nonsense values in the MappedName and WndClass properties. Our older scripts all run correctly, because they use the WinFormsObject("xxx") format. Has anyone seen this behaviour in TestComplete? Also, how does one set up TestComplete to record scripts using the older WinFormsObject("xxx") format?18KViews0likes9Comments