Telerik Test Studio Tip: Use Recording steps as many as you can

Best practice is to give high priority to recorded steps and low priority to coded steps. Only recorded steps will consume all changes happens on element in Element repository but not coded steps. As an example,  If we rename the element in element repository, changes will be effected automatically in recorded steps but not in the coded step. If we have an element in UI for which identification logic will dynamically effect based on user input, then we generally go with coded steps. However, best practice is to use concepts like bindings and make those steps as coded steps. One more important feature which we have for recorded step but not for coded step is reverse highlighting. i.e. if we select recorded step in test case then the corresponding element in the element repository will be highlighted.  Above mentioned are only some points, we have many advantages for recorded steps over coded steps.