First of all I want to thank you for detailed mail. For the moment I'm not interested to make fully functional test scripts, I want only to record/test almost all the UI objects from our applications in order to see that they are recorded and converted correct (that's way I need multiple conversions). I already found a problem/bug (http://www.telerik.com/automated-testing-tools/community/forums/test-studio-express/general-discussions/573342.aspx
) which will be released in the next internal release. I don't want to buy a tool which doesn't cover our needs and to be honest it is not very cheap. After I finish this phase I want to test a bit performance and load parts because even those two are very important for us. As I said we decided to start the evaluation of your tool because we already using some controls from your company (first point) and the second point is that it supports a lot of technologies and the third point is that it contains performance and load testing.
Regarding writing vs recording test scripts topic, we prefer to have coded tests approach because:
1) we could integrate our test with our continues integration build and run them as "unit tests"
2) we can run those MS unit test (or other formats) very easy
2) it is more easy for our envelopment team to make review and maintain them (in case it is necessary)
3) sometimes it is more easy to customize your code when it is coded
4) (from my opinion) a good test engineer should have almost the same programming knowledge as a developer
I know that in the beginning it is more easy and quick to make test using record and play functionality but after you have structured a but your tests (i.e. each screen is a class, each action over a UI object is a method) it is very easy to create (and to maintain) tests, is like completing a puzzle.
Thanks in advance and have a nice day