No viable alternative at input 'Element'

Technology specific object identification, supported applications, web technologies, and 3rd party controls.
deepak1920
Posts: 19
Joined: Sat Feb 13, 2016 5:04 pm

No viable alternative at input 'Element'

Post by deepak1920 » Tue Feb 14, 2017 3:21 am

Hi,

For last 2-3 days, my test is failing with below exception -

Ranorex.RxPathException: Parsing RxPath 'Element not found with XPath -

/form[@controlname='NewLogin']/?/?/link[@controlname='GooglelinkLabel']/?/?/link[@accessiblename='View all Google Fonts']' failed.

line 1:30 no viable alternative at character ' '
line 1:0 no viable alternative at input 'Element'

This is random failure. Most of the time I don't see this exception. But for last 2-3 days this exception is coming intermittently.

Can someone help me here?

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 3914
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: No viable alternative at input 'Element'

Post by odklizec » Tue Feb 14, 2017 8:29 am

Hi,

I'm afraid, without at least Ranorex snapshot and exact error (ideally entire report with enabled Debug report logging), there is not much anyone here can do for you. If something started to fail in your tests and you are using the same Ranorex version, then there most probably changed something in your AUT or test environment?
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration