Please suggest on using tellurium approach and queries

[ghanshyam baheti]

Hello,

We have been using Tellurium from last 4 months and running our written test cases everday. While running the test cases we are facing a problem.

 

Our Project SetUp :-

In our project we are dealing with more than one application(3 to be exact). 
So our one test case does the following steps and in each test class we are having 8-10 such test cases.

 1. Login to application - 1 (by openUrl)
 2. Fill/Enter data
 3. Log out of application - 1
 4. Login to application - 2 (by openUrl)
 5. Check the values entered in application - 1
 6. Edit/Enter new Values in application - 2
 7. Log out of application - 2
 8. Login to application - 3 (by openUrl)
 9. Check/Verify data.
 10. Log out of application - 3
 
While running the last testcase in test class we have 40-50 maximum browser instances opened, which slowdowns the system.
Some of the test cases fail frequently giving Timeout error.

Below is the approach we are using in tellurium.
1. Using connectSelluniumServer method in setup (@beforeClass).
2. Using disconnectSelluniumServer method in teardown(@afterClass).
3. Currently we are using openUrl to connect application Urls.
4. Using waitForPagetoLoad(100000) and waitForElementPresent('UID', 100000) before doing operation on element.

Can you please suggest.
1. Is above approach good to use?
2. what is best to use in the scenario explained here. openUrl  or connectUrl? Or is it ok to go ahead with openUrl?
3. Can you tell us the reason why we are getting  Timeout error?

Thanks in advance..

 

--
Thanks,
Ghanshyam Baheti.
-------------------------------------------------------------------