| || |
Txt checkpnts fail because QTP sees AUT vals wrong
I'm rushing through my automation today for a hotfix and an odd problem has surfaced. My text checkpoints are failing because QTP is seeing something odd in the actual value. These checkpoints have worked for quite some time, I believe the problem is limited to one machine. The problem is that the checkpoint fails because it says "expected 1" and actual is "II-". I look at my AUT and the expected of "1" is what is actually there.
If I change the checkpoint to a standard checkpoint rather than a text checkpoint, QTP sees the value of "1" correctly.
Does anyone have any idea of why this might be happening? That is, before I log a call with HP support and they start asking hundreds of irrelevant questions and ask me things I've already said. Sorry, had to vent.
Re: Txt checkpnts fail because QTP sees AUT vals wrong
Another public service announcement.
was set to Windows API then OCR on the machines that worked and on the machines I have that didn't work, it was set to either 'OCR only' or, 'OCR and then Windows API'.
Looking through my log files I see that this ran OK on several machines so I believe it was set correctly at one time. No idea of how that setting was changed.