Error Handling settings
Hello,
I upgraded to TestComplete 14 and noticed a change on error handling during playback.
I setup my default and current setting to handle the On Error as Continue running.
When I looked...
Forum Discussion
Hi kimmatsumoto,
Please refer to the following article - it contains a detailed table of the properties' changes implemented in TC 14:
https://support.smartbear.com/testcomplete/docs/general-info/migrating.html#runtime-properties
You will need to update the properties ones.
Hello.
So from my understanding is that you are saying that if you have upgraded to testcomplete 14 you will then need to go to each individeal test in test items and manually change the onerror setting from stop test item to your preferred setting you had before testcomplete 14?
If the above is correct and you have say hundreds or thousands of individual test cases then that is a big ask for testcomplete users to do. Was any consideration at smart bear given to fact that testcomplete users may have such situations. I am one such user and yes I can change the MDS files. However the purpose of testcomplete is to make test automation easier. For those who may not have the skill set to change MDS files how is changing On error setting for 100s or 1000s individual test items easy.
David.
That is why "What's new" documents are created, to inform you of changes. In the What's New for TC 14, we see this: https://support.smartbear.com/testcomplete/docs/general-info/whats-new.html#better-error-handling. So, to answer "Was any consideration at SmartBear given to fact that testcomplete users may have such situations?" Is... YES. THAT'S WHY THEY DOCUMENTED IT.
Just so you know... this actually was something discussed and frequently mentioned by a number of people here on the forums, requesting a better error handlng algorithm to give more granular control over test execution. So... it was documented... and in the documentation it lets you know "the behavior will change". It is a welcome change because it allows the developer of the project to be able to more directly control, via test item, when the runner will stop and at what level.
I'm sorry it's inconvenient for you (why am I apologizing? I'm not a SmartBear employee) but that's why documentation exists so that you are made completely aware of upcoming changes. Honestly, once you make the changes, it WILL make testing easier.
Happy automating!No one asked you to apologise,.
I get that you are not a Smart Bear employee, thats why you can be rude and condescending. No cost to you.
So if you read the update documenation and dont like its to bad for you and dont upgrade.
Ok I get it. Dont go on the forums so as not be talked down to and treated like an idiot,.
We will give consideration as to whether we should renew our licenses due to your reply.
I will flag it to our local rep.
Cheers.
Hi David,
When opening a project created in previous TestComplete versions, TestComplete 14 converted properties to the most suitable values. However, please pay attention to the fact that the new behavior differs from the previous one. Thus, you may notice different behavior of the test run. In this case, modifying properties is required. Sorry that this bothers you.
The main goal of these changes is to provide you with a better mechanism to handle errors during test execution. I hope you enjoy the new functionality when all migration steps are finished.
