Hi Nick,

Sean is correct - the fix is included in the latest internal build version 2019.1.307 and this can be downloaded from your Telerik account here. In case you face any troubles, please do not hesitate to get in contact with our Support service. 

@Sean: Thanks very much for assisting us in this thread. 

Regards,
Elena Tsvetkova
Progress Telerik

Hi all,

We are expecting to have an Internal Build released this week (5-7 March) 2019, where the change will be available.

Please make sure to turn on your Check For Update setting to look for Internal Build updates also and you will have automation notification, when starting Test Studio that the new release is available.

Best Regards,
Daniel Djambov
Progress Telerik

Hi Dan,

Please, excuse us for the caused inconvenience. 

However, the good news is that the issue is already resolved and will be available in the next internal build, which is planned for the upcoming few weeks. 

Thank you all for your patience and understanding. 

Regards,
Elena Tsvetkova
Progress Telerik

Hello Sean,

As the proposed workaround is really time consuming and you do not have sufficient time to spend right now, the other possible approach will be to rollback to the previous version of Test Studio. Please ensure all components are completely uninstalled before you get to installing the previous release - Test Studio standalone application and all Run-time editions installed on the execution machines. Then, selecting the correct version, download the full product installation from your account here and the Run-time edition here. 

Please accept our sincere apology for the caused inconvenience once again. 

Also, have in mind that I have converted the current support thread to a public bug report as the issue is on our end and we will work on resolving this as soon as possible. 

Thank you for your understanding in advance. 

Regards,
Elena Tsvetkova
Progress Telerik

Hi Sean,

Thank you for contacting us. I am sorry to hear you have encountered any misbehavior with out latest official release and will share some details on that. 

Lately we've been working on improving the Scheduling service stability in general and the current R1 2019 release introduces, recovery for the execution clients, improvement the communication flow between the different components and other enhancements in the scheduling behavior in overall. With all of these we have improved the responsiveness of the execution agents and it seems the tests included in a static test list are not always following the order from the list during execution. 

I suppose you have included tests in the test lists, which you expect to follow the listed order when executed. However, in this release the execution order may not always follow the test list order. As this is a major change in the behavior, we are already working on adjusting this to work as it is expected to. I hope that quite soon I will be able to get back to you with a permanent solution. 

In the meantime there is a workaround you can apply until we have a solution to continue using the current setup you have built so far. To ensure the order of execution, you can create a parent test and include the necessary tests in the desired order to be executed as steps. Then, insert this parent test into a new test list and use it to run the tests in the expected order. 

Please excuse us for any inconvenience caused and in case of any questions, do not hesitate to get back to me. Once there are any news on this case, I will get back in contact with you. Thanks in advance for your understanding. 

Regards,
Elena Tsvetkova
Progress Telerik