Improve reporting in transducers generative test.

Description

If the transducers generative test breaks, you get output like this:

This has a few problems:

  • when clojure functions are given as arguments, they're full object printouts, with classnames and memory addresses, this is kind of hard to read

  • the combination of the first problem found with the shrunk version means there's a lot of content to read

  • lack of pretty printing makes that content very hard to read

  • the traceback isn't actually that helpful – we know what failed already.

Approach: The attached patch encodes more descriptive info in the actions and does a better job of reporting the difference in an understandable manner:

Patch: transducer-reporting-v1.patch

Screened by: Alex Miller

Environment

None

Attachments

1

Activity

Show:
Completed

Details

Assignee

Reporter

Approval

Ok

Patch

Code and Test

Priority

Affects versions

Fix versions

Created December 21, 2014 at 10:16 PM
Updated January 9, 2015 at 2:27 PM
Resolved January 9, 2015 at 2:27 PM