IE-11 Browser Setting Issue
Hi, I need a help on this, until yester the test was running and recording fine, after I change the setting IE-11 (follow the steps from Preparing Internet Explorer for Web Testing) old test not r...
Forum Discussion
So... you have the following code:
propertyPageObj.FindChildByXPath(suiteVariableObj.txtboxStreetNum).Keys("661")
So... the question is... what does your code do if it is unable to find the child object?
See, if it can't find the object, then propertyPageObj.FindChildByXPath(suiteVariableObj.txtboxStreetNum) returns a null object... basically, nothing... so, it can't execute the Keys function... because there is no Keys function on the null object.
Better coding practice is to first check to see if you find the object before you try any processes against it.
My guess is that the XPath is different on IE11 than it is on Chrome... hence why it's working on Chrome. So... if the XPath is different, the function will return null, and your code will error out.
Double check the XPath in the IE environment. I'm betting it's different... in which case, you're going to need to go a little fancier with your suiteVariableObj.txtboxStreeNum and actually make it "smart" to detect the browser type and return a different XPath.
Hi Robert,
Thank you for your reply. My first two lines (highlighted) just put values in text box, the third one enter a value and than select dropdown list. Errors didn't happen always. Sometime happened in the first line, sometimes on the second one. It's randomly happened. I increased delay time from 500ms to 2500ms, they work now.
You mentioned that Chrome and IE11 xPath may different. Just wondering that IE10 and IE11 xPath are the same or not.
Thanks,
Yabing
eh... I REALLY don't like hardcoded delays like that... what if you move your test to a slower computer? That will mean you need to update your delays AGAIN. Or, if you move it to a faster computer, now you have these delays in there that are longer than necessary and you tests won't run as efficiently as they could.
I stand by what I said... if there is any doubt that an object is available before you move on, then you need to do a check on "Exists" before you attempt to use the item. You're using FindXPathChild which makes it trickier because it won't return an object you can check easily... all you can do is check to see if it returns null and then run a loop until it is NOT null.
As for the XPath difference... I don't know, really. That's something that may take some investigation but the possibility is there...Hi Robert,
I don't like hardcoded delays neither. Does TestComplete provide explicit wait like selenium?
Thanks,
Yabing
Hi,
> Does TestComplete provide explicit wait like selenium?
Yes it does. Look for the WaitXX() methods in documentation (e.g. WaitChild(), WaitAliasChild(), WaitSwingObject(), ...).
Unlike Selenium that throws exception if the sought for object was not found, TestComplete returns an empty object with the only Exists property set to True or False. You should check the value of this property and branch test code accordingly.
