Hi, this is a potential workaround, but it's really ugly : you need boolean variable in your project "testPassed". Each test case initialize this variable to false. And at a last operation, each test set this variable to true.
Then in the OnStopTest event, check both variable. If Log.ErrCount > 0 or testPassed = false : don't log perfs in SQL.
I haven't tried it but in theory it should work.
eykxas wrote:Hi, this is a potential workaround, but it's really ugly : you need boolean variable in your project "testPassed". Each test case initialize this variable to false. And at a last operation, each test set this variable to true.
Then in the OnStopTest event, check both variable. If Log.ErrCount > 0 or testPassed = false : don't log perfs in SQL.
I haven't tried it but in theory it should work.
eykxas Thank you for your idea. This way i could solve the problem but this is indeed not ideally.
I created a feature request (https://community.smartbear.com/t5/TestComplete-Feature-Requests/Clicking-on-Stop-Button-should-raise-Log-ErrCount-by-1/idi-p/250413) as rraghvani suggested and hopefully it will get some attention from smartbear.
In my opinion this behaviour of testcomplete should be seen as bug because a manually stopped test should also be markable as failed by checking Log.ErrCount within GeneralEvent_OnStopTest but at testcompletes current state its not.
