The translator handles the important actions and provides the necessary verifications for the control it is built for. The translator also describes the actions and verifications as you see them in the Test Explorer. Each action and verification actually has an element behind the scenes, the one you have recorded that step against. That element is part of the visual tree in Silverlight, or the "DOM" meant by you in your initial question. You can take a look at the Elements Explorer
window in WebUI Test Studio v1.x as well to check the elements in the repository you've recorded tests against.
WebUI Test Studio v2.0 comes with intrinsic translators for all the standard Microsoft Silverlight controls like Buttons, TextBlock, CheckBox, even Slider, Calendar, DataGrid, etc. In addition, it provides the RadControls Translators so that you don't have to inspect the visual tree yourself in order to build your tests. The translators over the complex components like RadControls help you work only within the Automation Surface (run the recorder), generate the tests and execute them. The video I pointed to you in my previous post demonstrates the typical translator in action very well. You can expect something like that in WebUI Test Studio v2.0 recording tests against Silverlight.
Thanks for your compliments about our videos, the interest in participating in the Beta testing and I really hope we can post some exciting news very soon.
Have a great weekend too,
the Telerik team