This is expected behavior and done by design. We cannot mark the test run as failed, because the run is triggered and there are no failures detected. In this case you need to analyze the test and try to determine why it's not executed. Looking the log and the screenshots I assume you are experiencing this issue when executing in Google Chrome and the problem is most likely that Test Studio is unable to detect our Chrome extension in order to start the automation. Please refer to this article
from our troubleshooting guide and see if this will help you to overcome the issue.
the Telerik team