Refer to https://support.smartbear.com/testcomplete/docs/reference/program-objects/ocrtextdocument/checktext.html or the example that JDR2500 has provided - the same can be done in Keyword Test.
I've wanted this for a long time but never put in a feature request for this. There is a 'Tools | Current Project Properties' which will allow you to chose what happens when your test had an error (do you want to keep running or stop that test and go to the next one). This is about the closes you will get.
However, there are some checkpoints which I would like to log as an error but continue running (especially image compares or flakey checkpoints I need to improve). It would be nice to have the option on each checkpoint, "do you (a) want to stop or (b) keep going". For me it would be nice for it to still show as an error though (or some indicator between error and warning ... something more critical than just a warning but not as critical as an actual error ... not red ... not yellow ... but maybe an orange which would mean 'flakey or bad coding or unreliable checkpoint which needs to be fixed/improved'). And OCR checkpoints can be flakey at times for sure depending, I guess on how the machine is feeling that day :|.
If you create a feature request for something like this I would definitely give it a thumbs up.
torus
I am using approach like you explain but, my project in in CI with Jenkins and results are viewed by non-IT people, who do not know, what status, whats mean and I want to manage statuses according to levels, for example:
if its passed in results log this statement would be green with explanation
red is failure with explanation and warning is failure of assertions and this approach help to identify warnings on OCR checkpoint.
