Telerik Test Studio Tip: Use Element repository as much as you can

Even though we can achieve  same test step without using Element repository, I would really suggest to use Element repository while writing test steps. Telerik Test studio provides powerful global Element repository with nice UI.  Nowadays every IT industry is moving towards Agile Methodology to develop modern web applications causing rapid changes in the applications in frequent manner leading to changes in the UI Elements day by day. It is tremendous pain for test case developer to update all test cases with updated Elements. In Element repository, an option will be provided to Edit elements which will take care of editing in all test cases where element exists. It will also provide an option to validate elements, where automation developers can understand all the elements that are changed in the UI in a single click instead of finding from failure reports after test cases are executed. Thus, user can directly go to that element and update it and it will reduce maintenance time for test cases drastically. In the same way it will provide a lot of options like Rename, Used by etc. where single change will effect in all test cases. I would also like to highlight that all the function which will work on repository element might not work on element  which we identified through coded step. As an example, assume we have SubmitButton in Element repository. Then:

Pages.PageName.SubmitButton.wait.forExists(3000);

will work perfectly but will not work if we write as below.

 <HtmlButton> submitbtn = ActiveBrowser.Find.byName<HtmlButton>(“submit”);

Submitbtn.wait.ForExists(3000);