Agree, I also meet such issues before, we may also need to create
utility class for that. e.g. assertSuccess(interpreterResult)
Alex Ott 于2020年6月10日周三 下午8:17写道:
> Hi all
>
> I was debugging multiple issues over the last day, and I've noticed that
> it's very hard to debug asserts like this:
>
Hi all
I was debugging multiple issues over the last day, and I've noticed that
it's very hard to debug asserts like this:
assertEquals(InterpreterResult.Code.SUCCESS, interpreterResult.code());
because it doesn't say what is the reason for it, just a difference. It
would be much simpler to debu