Add integration test for Vonnegut.Types about primer HOT 5 CLOSED

hackworthltd/vonnegut#89 gets us part-way there, by testing encoding and decoding of the same specific cases on both the frontend and backend. I think we should still do the following:

• property tests for encoding/decoding, or at least exhaustive tests of all sum type constructors
• integration tests that hit the actual server

from primer.

I'd like to leave this open because the additional coverage would be great to have (and I don't think it's hard to do). I'll remove the high priority label though, as hackworthltd/vonnegut#119 gets us 80% of the way there.

from primer.

We currently have a small test (in the frontend main app) that Haskell-encode/PS-decode works, but not the other way around.

In any case, it would be nice to move this out to proper property-based tests.

from primer.

Should we close this now? Or do you want to leave it open for the additional test coverage?

from primer.

I think this is more or less irrelevant now given all the backend API changes and the frontend rewrite.

from primer.