If I were you, I would depend on the assertions rather than the logs.
Of course, the logs are useful if you want to know what happened at certain point post the execution of tests. But, can't use the logs at run time to make decisions.
In case of Data Driven tests, assuming that the data in a file, even if data of particular row / record is failed, the retest has to be happened for entire data set, and hope you agree on this.
I am using assertions very extensively in each script. Neither am I using logs to make decisions. I also agree with you that if a failure happens, the retest has to happen for full data set. But that's not why I (or my team) is entirely using the logs.
We are using logs for two purposes. As test results and to look back and understand what all paths are taken in previous scripts (if there is a failure). There are too many parameters that we have to consider during debugging. So we use individual scripts status, overall test status, assertions, logs all (and each serve a particular purpose).
The problem now is when I want to schedule health checks, all test steps where we are using logarea are failing. Is there is a solution (or workaround) that we can use?
Thanking you once again for your time and support.
