You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The root README visible from the project homepage explains the various stages of work involved in order to run these tests. We convert existing sources of test data into a JSON format when we're creating test cases. We also write the result of executing each test cases in a JSON format. We create schema files using JSON Schema to define what structure of JSON and/or what values in that structure are valid.
For every "component" of functionality in our internationalization (i18n) library that we test, we have a separate structure for input and output data, since the corresponding APIs for each functionality component are different from each other. Examples of functionality components are number formatting, likely subtags (locale identifier maximization / minimization), and language display names. These functionality components will be represented in our test result dashboard as separate rows.
Code and test data have been added (or are in the process of being added) to the repository for the components like datetime formatting, list formatting, and relative datetime formatting.
This task represents configuring the schema validator to validate the JSON schema files for one of these new components, and to validate test input data and output test data using those schema files at runtime. These components code and test data are being added in #183 . Existing components should already have their input and output test data validated using the schema validator.
Requirements
a Debian/Ubuntu Linux system
python3 installed
the jq command line tool installed
Details
schema files exist in the schema directory, which is further subdivided into folders based on the identifier for the component
the full end-to-end script is at generateDataAndRun.sh. The schema additions must work and be executed by the end-to-end script, such that the script successfully runs without errors up through to and including the point where it runs check_schemas.py and check_generated_data.py
No description provided.
The text was updated successfully, but these errors were encountered: