Edited lookupExpectedValue to also take a List<String> errors in order to add the logged errors relating to "Received unexpected output" and "Matched expected output but at incorrect position" to the exception message
Also corresponding with
MRUNIT-48 throw more meaningful error for Received unexpected output when key, value actual class doesnt match any of the expected classes under the assumption that only one concrete class (no subclasses) is used for the key and one class for the value.
Updated tests to pass based on the exception message changing
committed in 1299567