When a piece of html text includes an ampersand character (&), the html markup encodes it as &. This markup is correctly included by telerik test studio when it views or verifies the element's InnerMarkup; but, this markup should be decoded when it views or verifies the element's TextContent or InnerText. The failure to decode the html markup leads to failures at verification.

Steps to reproduce:
1) Identify a screen element whose text content includes an ampersand (see attached screenshot 1).
2) Using the Edit Element dialog, examine the element's InnerMarkup - it correctly includes the marked-up ampersand as & (screenshot 2).
3) Using the Edit Element dialog, examine the element's InnerText and TextContent; they fail to decode the markup, so the ampersand is still included as & (screenshot 2). This is wrong - these fields are supposed to be free of html markup, just with plain text.
4) Construct a testcase which verifies the TextContent of the element; it fails because the plaintext ampersand & fails to match the mark-up ampersand & in the TextContent (screenshots 3-4).

The failure is recorded in the log like this (also included in attachment 5):

'29/08/2013 16:59:31' - 'Fail' : 16. Verify 'TextContent' 'Exact' 'Patient A. & E. Number' on 'HelpDialogHeader'
------------------------------------------------------------
Failure Information: 
~~~~~~~~~~~~~~~
Content.TextContent of 'HelpDialogHeader' does not match!

   Match Type: 'Exact'
   Expected Result: 'Patient A. & E. Number'
   Value at time of failure: 'Patient A. & E. Number'