Added Tests + Schema Updates

[natalialuzuriaga]

Problem

Another round of schema updates plus a new feature: added tests!

Solution

• Schema: Made values lowercase in CMS schema
• Schema: Add languages as a required field to generic schema since it can be easily automated
• Updated this repo's code.json

Added tests to validate examples against the generic schema and CMS schema using thejsonschema CLI:

• test/gov-schema.json validates CMS code.json files for compliance with the generic schema
• test/cms-schema.json validates CMS code.json files for compliance with the CMS schema
• examples.md point to tests and is up-to-date
• Updated json-schema-tests workflow

This will assist us with keeping the repository up-to-date as we continue to make changes to the schemas in the future.

Result

Thanks to json-schema-tests workflow. every PR will run the 2 test suites defined in /schemas/test

Test Plan

json-schema-tests passed!

[decause-gov]

I left a bunch of comments and questions in here, so I'll wait until we discuss then approve :)

This is foundational work Nat, thank you for leading the way 💡

[decause-gov]

Perhaps I'm not understanding how these test work, but should we be reading these examples from elsewhere, like the actual schema file in the repo? If that's not a simple thing, then having it in two places is prolly fine, so long as we remember to update it in both places, but if we don't update both, then would it show the tests passing even if the examples or schemas outside the test have changed?

[natalialuzuriaga]

True, we would have to update in both places. Re-reading the jsonschema CLI docs, I'm realizing that I can separate each test case in its own json file. I will rework the way we show our examples/tests then!

[decause-gov]

Thanks for answering all the questions. LGTM +1 🚢