Hello,
earlier I used to only IE for my tests.
A few days ago I tried to run my tests on Chrome and Firefox and found that they were slower. More time is required to execute them. For example, the same test list takes 28 seconds on IE but 77 seconds on Firefox and 72 seconds on Chrome.
Please, could you help to fix this problem? What reasons are for this behavior?
I use Windows 10 x64, TestStudio v2017.3.1206.0, IE 11.483.15063.0, Chrome v63.0.3239.108 (64bit), Firefox v57.0.2 (64bit). For Chrome and Firefox the latest extentions are installed.
7 Answers, 1 is accepted
Thank you for reaching us out.
We haven't observed such misbehavior in Chrome and Firefox and it is quite odd to get such a feedback. Could you please double check if this related to the custom application under test? It might be slower when running in these two browsers and thus the tests become also slower.
Could you please also record any sample test against a public accessible page and check if the slowness could be reproduced?
Thank you in advance for your cooperation! I am looking forward to hearing from you!
Regards,
Elena Tsvetkova
Progress Telerik
Hello Elena,
Unfortunately, I didn't have free time to answer earlier.
So, I see next. Our application works faster on Chrome than IE. I see it using my eyes and can say that refresh of contents, pages rendering are faster, absolutely if the browser is not run by Test Studio for tests. If so, loading of the main page and any other work with the pages is slower. Much slower because I can see it my eyes.
I checked on https://telerik.com too. The main page loaded faster if the browser is not run by Test Studio for tests.
I made a very simple test project for you. The test loads https://telerik.com page, clicks on DOCS link and waits for some elements as visible.
I run one twice and see something like that results.
Test duration: IE Chrome Firefox (in seconds)
10 72 40
You can see the results in the attached project.
I tested the project on two environments:
1. Windows Server 2012R2, IE 11.0.9600.18793, Chrome 64.0.3282.186 (64-bit), Firefox 58.0.2 (64-bit)
2. Windows 10, IE 11.248.16299.0, Chrome 64.0.3282.186 (64-bit), Firefox 58.0.2 (64-bit)
For Chrome was used "Progress Test Studio Extension 2017.3.1003.1"
For Firefox "Progress Test Studio Extension 2017.3.103.1" by Deyan
I need fix this problem as soon as possible.
Thanks.
Thank you for your feedback.
I reviewed the sample project you have prepared and here are my comments on the reported topic. The way Test Studio interacts with Internet explorer and JS browsers (Chrome and Firefox) is significantly different. This is why you see these discrepancies in execution against the different browsers. The extensions used for the JS browsers executes Javascript on the page under test which takes time and slows down the web page. Unfortunately that delay is by design and there isn't much we could do.
Though it is important to note we are continuously working on improvements in the extensions and I hope soon we will introduce new versions which will be working better as per your expectations.
Thank you for your understanding!
Regards,
Elena Tsvetkova
Progress Telerik
Are there new extensions for Chrome and Firefox so the execution time goes faster? Right now it's time consuming to wait for the script to execute in Chrome and Firefox.
Thanh
Thank you for reaching us out. Currently there are no new extensions for Chrome and Firefox - the latest were issued last October.
Please note the above shared information disclosed to Ivan why there are differences in the executions against the different browsers. We are always working on improvements across our whole product though there are areas which we hardly can improve.
Thank you for your understanding!
Regards,
Elena Tsvetkova
Progress Telerik
Hi Elena!
I am having the issue Ivan mention. I have to wait a long time for my scripts to finish in Chrome and Firefox against our website. At least 4 or 5 times slower than IE. It's worst in our testing environments.
Thanh
I do understand your concerns. Though the design of Google Chrome and Firefox defines our approach to support these browsers.
As I mentioned earlier in this thread the way Test Studio interacts with Internet Explorer, on one hand, and Chrome and Firefox, on the other hand, is significantly different. The extensions used for the Chrome and Firefox browsers execute JavaScript on the page under test which takes time and slows down the application. Thus you see that slowness in the execution. Unfortunately that delay is by design and there isn't much we could do.
I hope the above information will be helpful to you. Thank you for your understanding!
Regards,
Elena Tsvetkova
Progress Telerik