A nice thing to try so that you can se how it works for yourself (this is how I did it)...record a series of actions, not too many - have a look in the object map to see if you have some new entries relating to the area you just recorded, then look at the script, the script should contain fairly simple language relating to the steps you just did, won't look too codey.
Now go and turn raw record on and do the same things again, have another look at the script, this will look far more complicated, but perhaps mean more to you, either way it will help you understand what testpartner does.
See what you think works best for you.
I have worked on 2 apps, one is beatufully coded and all the objects get lovly names and it all looks easy and simple. Another app is difficult and old and nothing seems to work and needs to be done in Raw record! It really does depend on the app.
TestPartner 6.3, Visual Tests
Application under test: Client/Server based, C# .Net App with Infragistics Presentation layer
Database: SQL 2000/2005