Fails to encode results to json due to non-string error objects being raised

[svermeulen]

I have a custom error table that I pass to error(foo). When I do this in a busted test, and then pass --output=json, it will just print nothing, due to an error that occurs in json.encode where it is unable to serialize function objects. I'm guessing that busted should run tostring(error_obj) somewhere to address this problem

[YaroSpace]

Reopening the issue:
I am getting Failed to encode test results to json: type 'function' is not supported by JSON when running a suite with pending tests. Pending tests have an attribute - default_fn which is a function (defined as function() end in busted `init.lua:71', that cannot be encoded into json.

[alerque]

PRs welcome. Just papering over this with tostring() is probably not going to help though because comparing the string ID for two functions (even with identical content) is going to turn up !=. Some extra consideration might be needed.

[YaroSpace]

Ok. Will investigate further)

[YaroSpace]

I have a custom error table that I pass to error(foo). When I do this in a busted test, and then pass --output=json, it will just print nothing, due to an error that occurs in json.encode where it is unable to serialize function objects. I'm guessing that busted should run tostring(error_obj) somewhere to address this problem

@svermeulen I know it has been a while, but can you tell me how to reproduce your issue? I am trying to pass a custom error object to error(), but I am not getting any problems.