Attempt to dump offending objects in assert_array_equals and assert_object_equals

[wpt-issue-mover]

Originally posted as w3c/testharness.js#227 by @pwnall on 19 Dec 2016, 20:58 UTC:

Both assert_array_equals and assert_object_equals check their arguments piece by piece (element by element / property by property). This approach is sufficient when the assertions pass, but has a side-effect that when the assertions fail, we get sub-optimal debugging information.

Please consider building the assertion failure messages for these two functions in a more deliberate way. For example, when comparing two arrays, I'd like to see their elements in a JSON-like output (bonus points for GitHub-like diff highlighting).

Solving this issue would make it easier to use WPT to understand the differences in browser behaviors, and to debug & fix interoperability issues. Thank you very much!

[annevk]

I landed a fix for assert_array_equals (with lots of help from @jgraham). assert_object_equals is best not used and we want to redo/remove it as per #2033 so I think this can be closed.