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 HED specification provides a JSON-based test suite at https://github.com/hed-standard/hed-specification/tree/master/tests, which provides a set of example data (including strings, sidecars, TSV files, and combinations thereof), which should pass, and expected errors for those that should fail. This validator should eventually support validating against this test suite in an automated fashion. This would not directly affect the validator's built-in test modules.
The validation could be implemented in two stages:
Simple pass-fail validation (without regard to the exact error code).
Validating the actual error code.
The text was updated successfully, but these errors were encountered:
At this point, #1 is the most important. The hed-python GitHub actions run the tests against the spec JSON as a separate step. We could do it that way for hed-javascript. As the spec is iterated and tests are added (as happened recently with tests for the deprecatedFrom warnings), we would not expect the hed-javascript to pass right away, but this is because it requires a new feature to be implemented.
The HED specification provides a JSON-based test suite at https://github.com/hed-standard/hed-specification/tree/master/tests, which provides a set of example data (including strings, sidecars, TSV files, and combinations thereof), which should pass, and expected errors for those that should fail. This validator should eventually support validating against this test suite in an automated fashion. This would not directly affect the validator's built-in test modules.
The validation could be implemented in two stages:
The text was updated successfully, but these errors were encountered: