Why do some extract actions have expectation properties?  Isn't the purpose of an extract just to get whatever value is set at the time and put it into a variable for later use (typically verification)?

For example, the RadDropDownList has the built in action of "Extract - RadDropDownList: all item count is '19'".  This creates a step like this: "RadDropDownList('ctl00_cphM_ecAddContact_ddlCategory')Extract item count into DataBindVariable $(CphMEcAddContactDdlCategoryDiv)".  The step properties have CompareType and ItemCount.

Interestingly, in my test of a drop down list with 19 items, I changed the ItemCount property to 999 and ran it and the step passed successfully.