Telerik: Hi Ewin - I understand your point and it makes sense. In case you hover over the failed test if we show the failure information (like in Quick execution is there is element find error or any other error) probably will help you identify the error quickly, along with having Test priority as option in Test Result grid - how does this sound? We have to figure a way to show multiple errors in case of multiple failing iterations and other specific cases though. If you confirm or add something more to it, I will fire a feature request to have this iterated by PMs and process it further.

Hi Ewin, 
I agree you have a good point. We actually have Test Case priority property, however it is not included in Result view filtering, so I will create a Feature Request for our PMs to considers best way to implement it. 

About your second question that you need to go to each individual failed test I will give you my personal opinion as a QA - you have to go to each individual failed test, as each of them can reveal some sort of problem - either in the automation test itself, or in the application under test. Having so much failures however as you show in attachment is not reasonable for debugging - when we run our automation for Test Studio, we run nightly about 500 tests and usually there are 10-20 failed tests that need to be analyzed, most often it is random failures and automation need to be fixed and stabilized. Over time, if an automation test is working for a long time it will not break unless application/environment changes. 
The other failures usually require to fix the steps around the failure - before or after so that automation is more stable. Writing an automation test and running it tens of times until it is in a stable state makes it finalized. 

Of course there are random failures, that require too much time to investigate and fix and are not cost effective. 
For cases like this, what we have implemented is the strategy of called by ourselves "Failed tests rerun" - after a test list is executed, we create runtime a new test list with failed tests from the list only and execute the failed tests one more time. That way we can reduce the number of random failures and automatically get less results to analyze for application failures. Of course from time to time you need to analyze the initially failed tests, which pass afterwards to fix the automation test and stabilize it, but this is not urgent and allows you to have more time and focus on real double failures only. 

We use our execution extension methods to prepare and execute the failed tests again - first we create a new Test List object:
public void OnBeforeTestListStarted(TestList list)
        {
            //execute this section only for the Automation project
            if (projVersion == list.ProjectId.ToString())
            {
                isCurrentProject = true;

                //prepare execution to re-run failed tests
                if (!rerun || list.TestListName.Contains("FailedReRun")) return;
                //create new TestList object
                failedTL = new TestList(list.TestListName.ToString() + "(FailedReRun)", "Automatic", ArtOfTest.WebAii.Design.TestListType.Automated);
                failedTL.ProjectId = list.ProjectId;
                failedTL.Id = list.Id;
                failedTL.Settings = list.Settings;
            }
        }
then we execute if there are failed tests - we execute tests either individually or as part of a Test List:
  public void OnAfterTestListCompleted(RunResult result)
        { 
            //Only execute if re-run failed tests is selected
            if (!rerun || !isFailed) return;

            //get the list of failed tests for re-run
            var failedtestnames = result.TestResults.Where(x => x.Result == ArtOfTest.Common.Design.ResultType.Fail).ToList();
            
            if (rerunAsList)
            {
                foreach (TestResult tr in failedtestnames)
                {
                    failedTL.Tests.Add(new TestInfo(tr.TestId.ToString(), tr.TestPath.ToString()));
                }

                failedTL.SaveToListFile(projRoot);

                StartAOTProcess(failedTL.TestListName.ToString() + ".aiilist", projRoot);
            }
            else
            {
                foreach (TestResult tr in failedtestnames)
                {
                    StartAOTProcess(tr.TestPath.ToString(), @projRoot);
                }
            }
        }

Hope this makes sense to you too.