Webaii performance

[Aga]

I'm running test in 4 browsers (Chrome, FF, IE and Safari). 
The navigateTo(url) method sometimes takes 3-5 sec but sometimes 15s.
I have AutoWaitUntilReady setting set to false. I run the same tests in all four browsers.
Can I decrease this (navigateTo) time? It can be 3-5sec but the problem is when it takes more than 5. I have time limit for each test so I can wait so long.

[Cody]

Hi Aga,

I'm not sure I understand the question/request. We have no control over how long a NavigateTo step will take. It's completely up to your web server how long that action will take. I'd be more worried about why, if it normally takes 3-5 seconds, why does it sometimes take 15+ seconds. If you can answer that question and "fix" it (or do whatever is necessary to eliminate such a delay) would your problem be solved?

Why did you disable the AutoWaitUntilReady? This sounds like a bad practice in general. There are an extremely few cases where this is required, but it should be used as an exception, not the rule.

All the best,
Cody
the Telerik team

[Aga]

I disabled AutoWaitUntilReady because in most pages I had timeout exception when I tried navigateto method.
I've got forum thread ticket where is more information about it.

Aga

[Aga]

I have no idea why it takes more than 15s. It's the same virtual machine, the same OS.

[Cody]

Hello Aga,

Are you dealing with an ASP.NET web application? Is it possible that this 15 second delay only happens the first time you try to hit the web server right after a fresh deployment of your web application? ASP.NET is known to have a significant delay the first time something hits the website upon deployment of a new build. This is caused by ASP.NET having to take the time to "compile" and cache all of the ASP.NET code built into the web pages. Depending on the size and complexity of the website this delay can be quite lengthy.

In these cases we recommend overcoming this problem by including a "prime server" soft of test as the first test in your test list. The only thing this test does is hit your website once with a very very long timeout (I've seen 3 minute timeouts by other customers). it's sole purpose is to force the website to prime itself and be ready for normal use where you would see your standard 3-5 second delay that you describe.

Best wishes,
Cody
the Telerik team

[Pankaj]

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.

[Asta]

Because of AutoWaitUntilReady my tests keeped failing randomly.. I removed everywhere i can find. it and now tests are a lot faster and test fail rate is lower.

[Pankaj]

Hi Asta,

I am running my scripts in VS.

Is test settings during debug mode is different from test settings during execution mode. A Object is returned NULL during RUN mode everytime, but the same object is identified in and script is working fine during debug mode. I am not getting why this is happening.

Thanking you &

Regards,
Pankaj

[Plamen]

Hello Pankaj,

This forum is for Telerik Testing Framework support. Are you running a framework test or you are using our Visual Studio plugin? If you are using our VS Plugin and you are running your test from Quick Execution then yes the test settings are different than when you are executing the test from Test View in debug mode. However if you are running a framework test, Visual Studio uses the same settings for execution and debug mode and you shouldn't run into this problem. 

To be able to help you further a local repro is needed. Please provide the means to reproduce the issue locally(either in your app or on a public site), so we can try to determine what is causing the problem when you are testing in execution mode. Alternatively you can record a Fiddler trace using FiddlerCap and send it to us in a zip file. A Jing video demonstrating the issue may also help me to better understand what is happening.

All the best,
Plamen
the Telerik team

[Pankaj]

Hi Plamen,

We bought Telerik testing framework license and we have written our scripts using Telerik Manager only. We are writing our test scripts using Visual Studio.

The object I am telling about is actually visible and object property is not changed at all. It is having same object property. But still., telerik manager is not able to find this object from my webbrowser.

The application is a Internal.. and I can forward you the fiddler log files. But I couldn't understand that the issue is not with the application/response. It is telerik which is not identifying the object

There's no refresh in the browser after changing the selection in selection box. But the grid data is loaded based upon the selection in selection box.
  > Table is identified before changing the selection but not after (during execution mode)
  > Table is identified before and after changing the selection (during debug mode)

Regards,
Pankaj

[Plamen]

Hello Pankaj,

Thank you for the detailed explanation of the issue, however we haven't seen such behavior before and it's never been reported. Without a local repro of the issue it's not possible to say why we are not able to identify the object. This could be a bug, but we really need to reproduce it in our source code debugging environment in order to find the root cause and fix it. Please send me the Fiddler trace so we can further investigate the issue.

All the best,
Plamen
the Telerik team

[Ganga]

Hi,

I have noticed this issue after upgraded testing framework version from 2012.2 1204 (Dec 4, 2012)
to testing framework version 2012.2 1420 (Feb 20, 2013). 

Same issue in all the browser (IE, Chrome, Firefox). 

I didn't change any code. I have only upgraded to latest version to run the same tests. The basic test for set value to an textbox control takes few seconds to set the value even though the page has been loaded and control was ready to set the value.

Thanks
Ganga S



 

[Plamen]

Hi Ganga,

I have configured two virtual machines with versions 1204 and 1420, but I'm not able to reproduce the issue you're experiencing. Could you please send me an executable test(in a .zip file) against a public site? I want to run that test on my VM machines and try to replicate the issue locally in order to investigate what is causing it.

All the best,
Plamen
the Telerik team

[Ganga]

HI,

Firstly: my apologies for late relay to the question.

I didn't try this test on the public web site. I will try first and then confirm the problem. I can able to run the test on next week.

Our application has been modified recently and it has lots AJAX activities on each page.

My test suite is really large. I can't zip into a file.

Happy Easter……

Regards,
Ganga S

[Plamen]

Hi Ganga,

Ok. We'll stand by for further updates from you. All we need is a sample test not the whole project. But if you want, just let me know and I can share a private dropbox folder for you to upload your project to.

All the best,
Plamen
the Telerik team