ContributionsMost RecentMost LikesSolutionsRe: Execution Plan - Count - Stops on Failure Alex, no that will stop running if one of the iterations fails. Re: Execution Plan - Count - Stops on Failure That will rerun tests if they fail, but I want to run the test 10 times no matter what. Execution Plan - Count - Stops on Failure In the Execution Plan there is a column called "Count". My understanding of this column is it will cause the same test to run that many times while the plan is being executed. I have found that if one of those test runs were to fail, no more of those repeat runs will be done, and the execution will move onto the next test, even if "On Error" = "Continue running". We are currently in the process of investigating some flaky tests and it would be really handy if we could get say 10 failed results for the same test in an overnight run so that we can compare them. I don't see any settings that would make counts continue even after a failed test, but it would be really nice if there was one. The only workaround I've been able to find is just adding the same test to the Execution Plan multiple times, which is a bit cumbersome. Any ideas on a setting that I'm missing? Is there a feature request somewhere that I could +1? Include Warnings in the Exported JUnit Log Looking at an exported JUnit log I have, it seems that warnings are not included in the results. Is there a reason for this? Is this something I can change with a setting? Could we get such a setting it added if not? Re: Line Numbers in Keyword Tests This would be good Re: WshShell "The system cannot find the file specified" I believe treating it as a string is the point? WshShell.Exec is meant to execute a string as a command I believe. Removing the quotes give the error that dir is not defined. Defining dir as a variable string results in the original error. WshShell "The system cannot find the file specified" Use of theWshShell in our test suite has suddenly stopped working and I cannot figure out why. I have written a simple test to hone in on the error: function test() { //Don't check this in WshShell.Exec("dir") } Running this function pops up the error Shell is the name of the script I have written this function in. It definitely does exist at the path specified (though I find it strange there's no file extension in the error). TestComplete is running as admin. This error seems to be happening no matter what the command is. To be totally honest, I don't fully understand howWshShell works. If there is something in the properties of the project that need to be setup in order for it to work there's a good chance that's been accidentally broken, but I can't find anything anywhere telling me what that setup is, so I can't check. Any help would be appreciated. Solved