title: Microsoft UI Automation Library Vs Coded UI Test
body: <p>I'm very much new to <code>Test Automation</code> kind of thing. Recently I've been assigned to a project where I have to write an application (or, a script may be, I'm not sure) that will automate the UI testing of a CAD-like WPF application which misses lots of <code>AutomationId</code>s.</p>
  
  <p>After doing a little searching on MSDN and other sources I'm a bit confused about whether I should use the <code>Microsoft UI Automation Library</code> or the new <code>Coded UI Test</code> feature included in VS2010. I'm not getting the clear picture of which one of these two applies in which scenarios, what advantages one has over the other and which one suits my purpose.</p>
  
  <p>Please shade some light if you have experience/knowledge on the matter. Thanks in advance.</p>