Won't Fix
Last Updated: 02 Apr 2020 12:49 by Dan
Boyan Boev
Created on: 17 Oct 2013 11:37
Type: Feature Request
OnBeforeTestListStarted and OnAfterTestListCompleted are not called in test list remote on execution client
The test list events are fired in case of running on the scheduling server, however the problem occurs in case of running on the execution client setup (out of the server).

Steps to reproduce:

1. Create your own execution extension.

2. Override OnBeforeTestlistStarted and OnAfterTestListCompleted.

3. Create a test list and run it remotely.

Expected: OnBeforeTestListStarted and OnAfterTestListCompleted are called.

Actual: OnBeforeTestListStarted and OnAfterTestListCompleted aren't called.
Posted on: 02 Apr 2020 12:49
Thanks for the explanation, Elena. I appreciate your quick response.
Posted on: 02 Apr 2020 12:01

Hello Dan,

You are correct that the current item in the public feedback portal dates back more than 5 years ago. Though, it's worth mentioning that the first comments from Konstantin Petkov, published shortly after the item was submitted, provide additional information about the occurrence. 

Let me share some further notes on the topic - the communication between the Test Studio Scheduling components on multiple machines is quite complex and thus some limitations may occur - such as the test list related methods in the Execution Extension. The reason behind this is that the Execution server (or the Test Runner) on each of the machines is only an executor of the tasks, which the Scheduler maintains. Thus, the only component which uses the test lists context is the Scheduler, the rest of the machines are only Execution clients and they work with single tests. 

Though, we, the Test Studio team, are always striving to provide assistance to our customers based on their particular needs, to improve the consistency of other useful features in the product, and when necessary, to find a suitable workaround for the limitation listed in this public item. In order to provide as much details as possible, we updated the above mentioned article with the known limitations in remote execution - hopefully, this is useful for anyone, who is now trying to implement such a solution in his/her environment. 

A possible alternative is to insert the necessary custom code to be executed in the methods OnAfterTestCompleted() and OnBeforeTestStarted() - that way any machine in the setup will recognize and execute the code. 

Having that said, I will be happy to continue the discussion, if you have any difficulties related to this topic. So, please, do not hesitate to submit a support ticket with further details about any troubles you may have encountered. 

Thank you for your understanding in advance.

Progress Telerik

Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.
Posted on: 27 Mar 2020 16:37

It's now 2020. Has this ever been fixed?




Posted on: 23 Aug 2016 10:41
I am facing this issue for OnBeforeTestStarted method as well. I am using executionContext.DeploymentDirectory to get the deployment directory and it's not calling at all while running test list via run time license
Konstantin Petkov
Posted on: 28 Jan 2015 09:21

We've added a new help article on how to integrate the runner with the Windows Task Scheduler:

Hope it's useful!

Konstantin Petkov
Posted on: 27 Feb 2014 13:45
Just a follow up for a work-around in case one needs to execute the test list on the remote machine as a whole and get the execution extensions notifications in regards to test list. You can do so by using the Windows Task Scheduler, but also please take into account the tests need to run in user active sessions. The following resource can help:

Konstantin Petkov
Posted on: 10 Feb 2014 14:11

I have slightly updated the title and description to point to the setup this problem occurs on. Basically the scheduling server is the one that has the context about test list execution and the events are fired in the test execution context (the execution servers).

To proceed further in addressing this one we really need to understand the context in which this need occurs. If you experience this please contact us on Telerik support ticketing system with details on your scenario and we will assist with the custom implementation as well as make sure we take it into account in regards to further development related to execution events notification.

Thanks for the understanding on the matter!