1. Be careful when you pause the recorder and open links
from any applications. i.e. when Recorder is in the paused mode in browser, and
if you open new link say from outlook, then in your test you will see 'Connect
to popup(<URL>)' step recorded.
2. Not suggested to rename .tstest files when you use coded
steps. Because coded step method name will be created from Test Studio file
name. (i.e. say file name is 'Test' then the coded step method will be
Test_CodedStep1()). So when you rename tstest file, coded step method name will
not be automatically renamed. You have to do it manually.
3. Ensure to close the browser that holds recorder when
visual studio crashes unexpectedly. Otherwise when you reopen the test and try
to run the test in already opened browser your visual studio will crash again .
In worst scenario even you need to restart the machine.
4. Pay attention while renaming or deleting elements from
Element Explorer in case if you have written some operations using elements in
coded steps. Because context menu options in Element Explorer works contrary on
the elements used in Coded Step.
Examples :
a. When you rename an element in Element Explorer, it will
not automatically rename the same element used in coded step.
b. Used by option will be disabled even though the element
is used in coded step.
c. Delete option will be enabled even though the element is
used in coded step. So be careful when deleting the elements in Element
Explorer.
5. If you are not able to open the .tstest extension files
in Visual Studio.
If you face such scenario, right click on the Test file in
Solution Explorer as shown in the screen shot and then choose 'Exclude From Project'. Then restart visual
studio. Right click on the Test file again in Solution Explorer, and then
'Include in Project'.
6. Ensure that you have launched Visual Studio as
Administrator, otherwise you will not be able to launch browser from Visual
Studio.
7. From Telerik Test Studio, when you open the Test Studio
project that is developed in Visual Studio, and if you open any test studio
file, immediately file gets dirty without any modifications.
8. Good to maintain project name as Namespace. You will face
challenges when you try to open the project in Test Studio that is developed in
Visual Studio using Telerik Studio plugin. create problem when
For Example you have project name as 'Demo' and you have
created Login.tstest file in 'nightly\tests' folder then your tstest file
namespace will be "Demo.nightly.tests" . So if you open this project
in Telerik Test Studio and open Login.tstest file, immediately that file will
be shown in dirty mode(even though you do not do any modifications) and when
you save it from Test Studio then the namespace will be modified to Demo.
9. Avoid using special characters (ex: &) in names for
.tstest files
10. More will be in a new blog. J
No comments:
Post a Comment