Question

Tosca Commander is behaving too slow at the start of execution and during the result log.

  • 21 February 2024
  • 6 replies
  • 234 views

Hi Community,

I am using tosca on AWS Workspace. While running the test steps in scratchbook, tosca behaves too slow to verify the licenses and start the execution. Also it takes a lot of time to log the results as well.

 

Could you please help me find the reason and improve this slowness?

 

Thanks,

Siddharth

 


6 replies

Hi,

I face the same. Sometimes it takes even more than 3 minutes for the execution to start, and the same when processing the results. This doesn’t happen every time, but often. Could anyone help?

 

You probably have many browser tasks open, which slows down the startup process. You can use the following steps to terminate these tasks in Tosca Commander. Take a look at the Task Manager details for the process names.

What to do next with example values:

  1. Search and Add TestStep: TBox Start Program
  2. Path: taskkill
  3. Argument: /im
  4. Argument: msedge.exe
  5. Argument: /f

Microsoft Taskkill Documentation:
https://learn.microsoft.com/de-de/windows-server/administration/windows-commands/taskkill

This happens to me aswell sinsc Tosca 2023.1.6. 

I only have 1 window open

Badge

Hello!

I have the same issue that is mentioned above. In my case, it takes around 30 seconds to enter first value in the application. We have 10+ users in the team and this issue has been observed only for a user. We use Tosca 2023.1.3 version. Closing edge is already part of the precondition.

Any leads to resolve this issue would be highly appreciated.

Many thanks!

Badge

Hello!

I have the same issue that is mentioned above. In my case, it takes around 30 seconds to enter first value in the application. We have 10+ users in the team and this issue has been observed only for a user. We use Tosca 2023.1.3 version. Closing edge is already part of the precondition.

Any leads to resolve this issue would be highly appreciated.

Many thanks!

Update:- This issue has been resolved after replacing user machine. I would suggest you to format your machine if you do not have any options to replace your machine. Many thanks!

Userlevel 1

We didnt have this issue with version 14.2, but had this issue with version 16.0 and 2023.1, and it is happening with everyone in our team

Reply