You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 19, 2018. It is now read-only.
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!
The text was updated successfully, but these errors were encountered:
Both
assert_array_equals
andassert_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!
The text was updated successfully, but these errors were encountered: