Hello Support Team,

I am exploring this tool.  I want to know what testing framework do you suggest with Telerik test studio?

Testing Framework can be: Modular Framework, Data driven, Key word driven, Hybrid.

As of now what I am doing is: I create tests and mark it as common test For eg: Login. I parametrized User Name & Password from database value. So I can say that I have hybrid(Modular + Data Driven).

But I am seen over internet that People talks about key work driven framework (in QTP). Where we have all details stored in excel file( Mapping of Keyword with object repository). Then they prepare some driver scripts to fetch testcase from excel file and execute it.

My point is that why to have key work driven framework if Telerik test studio has common object repository, and facility to check/ uncheck steps in testcase?

I want to know what do you recommend?

If possible can you please provide me demo project with ideal/expected framework ? Sorry If I am asking too much.

Regards
Karan Patel

Hello Karan,

Your questions are very good, and are common ones asked by people familiar with other testing tools.

Would you mind if we first made this discussion thread public so other Telerik.com forum readers could see it? This is very useful information for other users too!


Regards,

Hi,

Yes, please make it public. I have no issues.

I am glad that my questions will help others. Because I feel there is no need to have key word driven testing framework with telerik test studio projects. This tools some good features.

Regards,
Karan

Karan,

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.

Regards,

Jim Holmes
Test Studio Evangelist