When i am creating the script for different modules like log in the application,client and rest of the modules.if i created the script for login application and save it.then after this i move to the next module, is it necessary to start recording the application from initial point i:e from login state or their is the way so that we can call the log in script from various modules by which we can save time as well as script steps will be less also.
Regards
Hillary
5 Answers, 1 is accepted
You can use the Test-as-step feature as demonstrated in this video.
Best wishes,Cody
the Telerik team
Rank 1
Thanks for the quick reply. I think the original post was not exactly clear in what we are looking for. Basically we are testing our web based application that requires user id and password to access the application. The issue we are having is that we have individual scripts and each time it executes the scripts it has to log in the application. We are wondering if there is a way to keep us logged into the application while executing a group of scripts. If the only way to do it is to use the data bind feature, than how do we call the user name and password that should be used to log in?
Can I assume that the user ID and password never changes, that you will always log on under the same account? If true, then skip the data binding feature. Create a "login.aii" test script that does nothing but logs in under that fixed account name, then have step 1 of all your other scripts call your login.aii script via test-as-step. Does that suite your needs better?
Mainly I pointed you to the video just so you can see the "test as step" feature in action. Feel free to ignore the data driven portion if it doesn't apply in your scenario.
Cody
the Telerik team
Rank 1
I thought we were using this feature and revisited the scripts and I don't know if it is being utilized. I will add it and see if that resolves our issue. If not we will let you know. Thanks again for your help!
Another feature that you may not be aware of is the "Recycle Browser" feature and may actually be what you're looking for. When you enable this feature and you're running a test list, the browser will remain open and be reused from test to test. With this approach your first test in the test list should be your "login.aii" test, then follow it with all your other tests that simply assume the user is already logged on. Don't use the test-as-step for calling Login.aii if you use this feature.
Greetings,Cody
the Telerik team