Patterns for UI test Automation

I'm currently automation a plugging for MS Office. We are creating Coded UI tests in VS 2010. As an option I could use the "Coded UI test buil开发者_运维百科der" tool, but it does not suite in my case. So I created my own UI Map class and extension methods for each UI Control/Map where i add different action functionality, for example press buttons or asserting some UI values. The scenarios of the test cases are in the test classes.

I am new in this area and also I'm new in working as a automation tester. May be you could share your experience or advice some good practices and practice for test automation (from a programming/design point of view)

The good practices that apply to test automation and design are the same as for good programming in general.

When you're coding for test automation, you should apply the same criteria for whether or not you apply a design pattern as for when you are coding in any other situation. There is no difference.

Here is List of 10 best practices for UI Test Automation:

http://fczaja.blogspot.com/2011/01/ui-test-automation-best-practices.html