Verify element text not "seeing text"

[Russ_Thomas]

@Paul_Smith1

Im confused about the Verify Element Attribute Value WebUI attributes and how to set them

You are right to be confused - it’s not your fault.

Firstly, In automation testing, you normally don’t (and strictly speaking, shouldn’t) set them - simple reason, regular users can’t set attributes so why should your automation code ever need to?

However, the value property (which is not the same as the value attribute) is set via setText (like I said, poor API naming choices) and is read back using *ElementAttribute APIs as you’ve seen.

So when you think you’re getting the value of the value attribute using verifyElementAttributeValue, you’re not - you’re getting the value of element’s value property.

Messy? Oh yeah. Hence…

Fix Poorly Named/Broken APIs

getAttribute This API will return a property when asked to retrieve the content of the value attribute. It will do this even when the value attribute is undefined! This is wrong, because… An element property is not the same as an element attribute. Note: Perhaps it always returns properties, I did not test that. Because there is existing test code reliant on the current behavior, the documentation should make clear this API is deprecated in favor of two new APIs which do the correct thin…