These tests include functional testing of the UI controls.They let you verify that the whole application, including its user interface, is functioning correctly.Such code can now do no harm and is safe to be displayed on a page or inside an e-mail. if quotes are escaped with a slash \ let's remove that.Sure, it may not look nice and tell you someone has been trying to mess with your script, but the important thing is he/she had failed! If you know exactly what kind of data to expect you can make further steps to ensure the user has entered what you want. Instead of writing the same code over and over again we can create a function that will do all the checking for us.Another thing I like to do is to display the validation error message on the form in an otherwise hidden field: The problem with our last solution is that if the user saves a partially filled form, and picks it up at a later time, that error message that popped up is long gone, and the only indication that there is something wrong with the form is the modified field color.So, having a text field contain that error message might be a good idea.There are other ways to highlight the field in question besides changing the text color, the border color or the fill color could be changed instead, or in addition, just make sure that you are not making the form impossible to read.
So, if the user enters ‘01234’ we should see an error message that would instruct the user about what type of data is valid for this field.
Note that if you have a remote mounted drive it's possible that it can look like you're the owner of the file, if the remote system has the same username.
This will prevent the above from working until you log in to the remote box itself.
Coded UI Tests are particularly useful where there is validation or other logic in the user interface, for example in a web page.
They are also frequently used to automate an existing manual test.
Search for validating user:
The latest version of this topic can be found at Use UI Automation To Test Your Code.