No Log.ErrCount when test is being stopped manually

Thank you for clarification. So the easy solution would be the child process to raise an error by default if the stop button is clicked and not the parent?

---

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.

---

rraghvani wrote:

Log.ErrCount returns the number of error messages (that is, messages added via Log.Error) posted to the test log during the current run of the current test item.

 

In this example, I'm calling Log.Error() method twice, and Log.ErrCount shows 2 

If I stop the automation after the first Log.Error() during the 10 seconds, then Log.ErrCount shows 1

Which is normal behaviour.

 

---

Yes i undestand that and thats the problem.

---

Which is normal behaviour.

---

Normal behaviour doesnt mean its good.

Log.ErrCount should be 1

Ideally the "The script execution was interrupted", which looks to me like a Log.Error should be logged at the time i click the stop button and not at the very end of the log. But probably thats not a thing smartbear is going to change in near future so i need to find a workaround for this.

Still not acceptable if the user has to find workaround and this makes it more difficult to work with testcomplete. Atleast give the user more control over such things by adding something that helps with such situations. Add more Global Events for example OnStopButtonClicked or OnStopTest or OnPauseTest etc.
I know its maybe a problem a minor portion of users will have but still (and this has not changed): Usability or ease of use does play a big role into customer satisfaction.

Inside of GeneralEvents_OnStopTest we are collecting performance data (test-duration, cpu usage of AUT, memory usage of AUT etc.) and log the data into our database. But this data should only be written into the database if the test is passed.

To determine if the test is passed or failed we defined a variable "ErrorStatus". This ErrorStatus variable will be set to 1 (for failed) if: GeneralEvents_OnLogError has been called or if Log.ErrCount is greater than 0

So we need to have the test marked as failed when:
1. Log.Error(...) occured --> GeneralEvents_OnLogError(...) was called
2. JScript runtime exception occured -> Log.ErrCount is raised by 1 but does not call GeneralEvents_OnLogError(...)
3. The test was stopped by user -> does not raise Log.ErrCount and test is marked as "Passed" inside of GeneralEvents_OnStopTest(...) -> Only problem left for me to solve

We use the performance data to calculate a percentage deviation to previous test runs (test-duration, cpu usage, memory usage) and in order to ensure that the performance data comes only from test runs that are initailly "passed" we have to prevent that data from a failed test is being written into our database.

And of course we do stop the tests every now and then especially if we have to debug and fix our test scripts.