For the recently published FGDC writer I build a library of functions to generate mdJson test scripts. Besides saving code space this should pay out when there are changes to the mdJson schema. A single change to the mdJson generator will automatically propagate through all tests for which it is deployed.
The changes will also provide:
messages issued from methods
support for ERROR/WARNING/NOTICE level messages
message text loaded from YAML files for easy changes and multi-language support
support for context added to message to identify source of issue
Readers to update:
[x] mdJson (partially complete)
[ ] FGDC (mdJson generator does not apply) (partially complete)
For the recently published FGDC writer I build a library of functions to generate mdJson test scripts. Besides saving code space this should pay out when there are changes to the mdJson schema. A single change to the mdJson generator will automatically propagate through all tests for which it is deployed.
The changes will also provide:
Readers to update: