Since starting to log test failures to the test server in 524ee26, the messages about failed assertions were displayed like this in browser console: Expected %o to be == to %o. This was because Evidence's `printf` was misbehaving and emptying the arguments array which was supposed to be forwarded to `console.log()`.
This fixes large, unsafe integers to be deserialized as numbers and thus their value broken because of overflow. This reverts #865 because it was a wrong direction to go in. The test assertion was broken in the first place because it used an unsafely large integer to begin with.
We often use `assertLength` for checking whether a Zepto collection of proper size was returned, but in some test a plain Array could also pass that check. Use `assertZeptoCollection` in places where an object is only subjected to a `assertLength` check but not any other tests.