Hi Doga Ercan,
I am going to suggest you may be making a common mistake that many QA engineer's make when they first start writing test automation... that of trying to put too much into a single test. From a high level there should be one test per use/test case. For example:
1) Can enter good data in all fields and successfully save the record
2) Bad data entered into field A yields error message A
3) Bad data entered into field B yields error message B
The above should be 3 separate tests. You might be able to modularize and reuse parts using our test-as-step feature, but if properly designed, you won't run into the problem you are asking about (how to make a test skip steps 15-20 and start over again with the next data iteration).
To answer your question, there isn't a direct way of making a test stop in the middle without a failure. The closest you can come is to use an IF-ELSE logical block, which can be nested if needed. Run some steps in the IF and others in the ELSE. This way the test runs to the end, but only runs the steps needed for that particular instance.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items