seanfitzg
15 years agoNew Contributor
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.
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.