Performance issue before opening the page into the browser
I've got some performance issues when the UI tests are executed into the release machine, on the initial phase execution: the browser is opened, but then it remains in Playback for lot of seconds (at least 15-20 seconds) before writing the url. Just to explain better:
- Test Execute is started
- The browser is opened (I'm using Edge)
- Test Execute remains with the "Playback" information, and the browser displays the browser home page (about:blank for me)
- after lot of seconds, the url is finally written and the page is opened
It appens only if I execute the tests on the release machine, it doesn't appens on my local machine.
What could be the reason why Test Execute takes long time to write the url in the browser and it remain in Playback status?
Thanks a lot
Solved! Go to Solution.
Hi @Marsha_R ,
do you think that it could be an issue coming only with Edge browser?
I've not the possibility to quickly try with another browser, but if you need a test I will do it.
Could be, but maybe first just check that your browser versions are the same on the machine where it works and where it doesn't. Since your test runs on other machines, we need to figure out what's different between those and the one where it doesn't work.
It is the same version on both machines: Microsoft Edge 87.0.664.75 (64 bit).
On the release machine (where there is the performance issue), I'm launching the tests using the "Visual Studio Test" task for Test Plan.
I think Test Execute is automatically launched by the AzureDevOps task, is it not so?
I've added the TestComplete test adapter installed, by specifying TestExecute:
and then the Visual Studio test task to run the Test Plan:
Is there any other way to get the real code that starts Test Execute, as you asked?
I would ask Support...
/Alex [Community Champion]
[Community Champions] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Champions]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Champion] signature is assigned on quarterly basis and is used with permission by SmartBear Software.