Youv'e hit on some fundamental differences in how basic test case strategy is thought of between Test Studio and other tools like QTP.
We don't have a keyword infrastructure like some of those other tools. Instead we give you powerful data driving support for input data and expected conditions. You can also use data driving for defining element locators on the fly. (I wrote a blog post
about that earlier.)
You can combine this approach with using a flexible find logic
for your locators to cover many of the scenarios usually associated with keyword testing. I think focusing your test cases this way keeps things much clearer so it's easier to understand exactly what your test cases are doing.
One note on checking individual test steps in a test to enable/disable them: I recommend against this practice except for troubleshooting. It's the same thing as using conditionals (IF-THEN-ELSE) in a test to change behavior of the test case. I think that's mixing behaviors in one test case, and I prefer to keep test cases extremely granular and specific.
Test Studio Evangelist