Closed jphill4 closed 1 year ago
Yes - this gap in the assert library arises from time to time and should be filled. It should be easy to add, and maybe I'll get to it this evening.
In the mean time, a workaround is to use
@assertTrue(all(str1 == str2))
but, admittedly, the diagnostic for failing cases is less informative that way.
I've done a quick and dirty PR (#385) but it does not give particularly informative failure messages. But at least the new interface are in place.
The AssertEqual package was contributed by someone else, and now that I'm looking at the code, I find it to be overly verbose and cluttered. I did a bit of refactoring now, but more is needed. When done, I can then reuse some of the scalar code to generate proper failure messages for the array case. I've marked the PR as "draft" for now.
Thank you for your work on this!
I would be nice to have an assertEqual overload for arrays of character strings. This did not work for me:
Reproducer attached. test.zip