1 Answer, 1 is accepted
0
Hi Sebastian,
Is that issue about the run being stuck there or just needs a lot more time to run the tests? We are aware of a performance degrade issue with this build due to changed local test list execution, which should be fixed with the next build expected early next week. As a simple work-around you can also switch back to the old scheduling setup dependency by editing the Telerik.TestStudio.exe.config located in C:\Program Files (x86)\Telerik\Test Studio\Bin.
In order to proceed, close Test Studio, open the config file in notepad and change the CommandLineRun value to 'False' as shown in the screenshot attached.
Regards,
Konstantin Petkov
Telerik
Is that issue about the run being stuck there or just needs a lot more time to run the tests? We are aware of a performance degrade issue with this build due to changed local test list execution, which should be fixed with the next build expected early next week. As a simple work-around you can also switch back to the old scheduling setup dependency by editing the Telerik.TestStudio.exe.config located in C:\Program Files (x86)\Telerik\Test Studio\Bin.
In order to proceed, close Test Studio, open the config file in notepad and change the CommandLineRun value to 'False' as shown in the screenshot attached.
Regards,
Konstantin Petkov
Telerik