I have prepared some test cases using Telerik manager and executing it daily.
Till friday, the overall execution time is 1 minute per test case (this execution time is captured for almost two months).

But today the same test case is executed for more than 5 mins. When I debugged the TC, I can find that, Manager.Current.ActiveBrowser.Find.ByExpression is taking more time than it takes usually.  It is taking almost one minute to goto next statement eventhough the object is already visible in the document. Please let me know what is this issue.. and please let me know is there any performance issues from telerik test framework?

Regards,
Pankaj.

Hello Pankaj,

Thank you for contacting Telerik Support.

We're not aware of any slow test execution problem as you describe. We'll need a way to reproduce this slowness you are experiencing. Can you send us your test along with a Fiddler trace of the application it is running against so that we can study the slow execution problem locally? If you are unfamiliar with how to create a Fiddler trace, this link will provide you with step-by-step instructions for download and use.

Regards,
Mario
the Telerik team

Hi,

Thank you for your response. I found that this performance issue is with the machine., after resarting the machine, slow performance is resolved. Kindly apologize me on that.

But I have one more issue with telerik performance. When I am executing my scripts in debug mode (in VS 2010) everything seems to be working fine. But when I am executing a test case in RUN mode, then I am recieving the object null reference exception. This is annoying me.

The scenario is like, when I am selecting a listItem in a selection box, browser will NOT get refreshed but the table below the selection box will get refreshed and data is loaded based upon the selection. I tried RefreshDomTree, and sufficient WAITFOR time to resolve this issue. But the table which is loaded with new data is not identified in RUN mode whereas working fine in debug mode.

Steps below
1. Identify target table using appropriate expression(--> it is not null)
2. Change the selection in the selection box.
3. Wait for certain period until data is refreshed
4. Try Identify target table using appropriate expression(--> this time it not null)
> loop for 5 times with 1 second wait and refreshDomTree every time before checking the Element again.

Regards,
Pankaj

Hi Pankaj,

No problem, I'm actually quite glad you were able to resolve the original issue yourself.

As for dealing with this second problem, from your description of the varied behaviors between executions, this null reference error sounds to me like a timing issue. On the other hand, your comment that you've tried adding 'sufficient WAITFOR' says otherwise and has left me uncertain.

In order to provide you with an exact solution, we will need to reproduce the issue locally using a copy of your test against a Fiddler trace of the application it is running against. If you are unfamiliar with how to create a Fiddler trace, this link will provide you with step-by-step instructions for download and use. Thank you in advanced for helping us advise you.

Best Regards,
Mario
the Telerik team