Hello Lokesh G,
Ok, guess I need to get one possible point of confusion cleared up... are we talking about the QA edition or the Developer edition? It sounded like Developer edition, but that edition does not include "Export to Visual Studio".
Yes you certainly can! Just click on a step and then look or open the properties window. You'll find all steps have a large set of properties for it. Some of the properties will change depending on the step type. e.g. SetText steps have a Text propert. NavigateTo steps have a URL property, etc. See the attached screenshot for an example.
If creating your own custom coded step from scratch, no I'm afraid not. Not a bad feature request though. The closest you can come right now is to select an existing recorded step and then convert it to code. The converted step won't be moved in the test sequence.
Unfortunately no, not at this time. We get that feature request very often. The good news is this feature is currently in development and you should be able to see it in some near future version... I just can't give any specific dates yet.
You have four possible routes you can take. On the "Add..." drop down is a "Delay Execution" option. The test will simply pause for the number of milliseconds you specify before moving on to the next step. The default is 250 milliseconds, but you can change it to be as large or as small as you need it.
Or you can change the properties of a step to say "Pause before" or "Pause after". This will cause the test to pause, display a dialog and not continue until you click the OK button on that dialog.
Or you can implement a WaitFor step. For example, you just clicked the Login button and you're waiting for the main page to finish loading. Determine which element shows up last and add a "WaitFor Exists" (best for HTML) or "WaitFor Visible" (best for Silverlight) step on that element. The test will pause until either the element appears or the step timesout waiting for it to appear. If the step times out, the test will stop and be marked Failed.
Lastly, if all else fails you can always add your own code behind method and do whatever sort of custom waiting period you can program.
Hope that helps,
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? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items.