JSON file based test suite #9
Description
What is wrong?
It would be good if we could standardize our tests into a set of portable JSON documents which describe the inputs and expected results for things like loading and validating packages and their internal data. This would serve as a framework for other languages which implement a similar library to ensure that everyone is developing against the same spec.
How can it be fixed?
Similar to how the ethereum/tests repository contains JSON based tests for EVM implementations, we should develop the same. We can start with them living in this repository and then move them to their own repository in due time.