Unity unit tests fail when an error is logged to the console.
Why would that ever be a good idea? We find it quite annoying. We want our tests to fail when the assertions we wrote are not fulfilled. We don't want our tests to fail when some code we don't control (or code we're not testing right now) decides to log an error message. A log message should just be a log message, nothing more.
This behaviour should be removed completely, or at least configurable. The only way to get rid of this behaviour is to actually expect an error log, with the same exact text. This makes no sense from a unit testing point of view. If we are testing function A, why should we know the exact error message logged by a distant function Z? We should only care about the possible results of function A.
Please make tests not fail when error messages are logged!