Actual and expect value match but fail

Ask general questions here.
[email protected]@
Posts: 18
Joined: Fri Dec 27, 2019 12:16 pm

Actual and expect value match but fail

Post by [email protected]@ » Thu Feb 13, 2020 10:06 am

Hi,
I am using window 10, ranorex version 8.3.1
When I validate value of a textbox, although actual and expect value does match but fail
Can you help me?
Attachments
Capture.PNG
Capture.PNG (51.61 KiB) Viewed 155 times

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

Re: Actual and expect value match but fail

Post by odklizec » Thu Feb 13, 2020 10:23 am

Hi,

At first, Ranorex 8.3.1 is pretty old and no longer supported. Please try to reproduce the problem with most recent 9.2.1. If the problem still appears in 9.2.1, then there is most probably a problem with some non-printable characters in the reference/compare string.

Could you please share a Ranorex snapshot (NOT screenshot) of the element you want to validate? Also, if you read the reference value from excel or csv file, please share it as well. My guess is, that there is a problem with "space" character between date and time.
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

umpani
Posts: 2
Joined: Wed Jan 30, 2019 11:03 am

Re: Actual and expect value match but fail

Post by umpani » Thu Feb 13, 2020 10:59 am

Hi,
it seems that you are validating that values have to be different each other and because values are same then it fails.

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

Re: Actual and expect value match but fail

Post by odklizec » Thu Feb 13, 2020 11:46 am

Ha! Umpani is most probably right! There is != in 'expected' value ;)
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