Test.Aeson.Internal.ADT.GoldenSpecs

Tests to ensure that JSON encoding has not unintentionally changed. This could be caused by the following:

• A type's instances of ToJSON or FromJSON have changed.

• Selectors have been edited, added or deleted.

• You have changed version of Aeson the way Aeson serialization has changed works.

If you run this function and the golden files do not exist, it will create them for each constructor. It they do exist, it will compare with golden file if it exists. Golden file encodes json format of a type. It is recommended that you put the golden files under revision control to help monitor changes.

same as goldenADTSpecs but has the option of passing a note to the describe function.

test a single set of values from a constructor for a given type.

The golden files already exist. Serialize values with the same seed from the golden files of each constructor and compare.

The golden files do not exist. Create them for each constructor.

Create the file path for the golden file. Optionally use the module name to help avoid name collissions. Different modules can have types of the same name.

Create the file path to save results from a failed golden test. Optionally use the module name to help avoid name collisions. Different modules can have types of the same name.

Create the file path to save results from a failed fallback golden test. Optionally use the module name to help avoid name collisions. Different modules can have types of the same name.

Create a number of arbitrary instances of a particular constructor given a sample size and a random seed.

Make a Golden File for the Proxy of a type if the file does not exist.