-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Message Format - Test Suite #109
Comments
Unfortunately i cannot assign it to you @grhoten , not sure why. but here is the issue we talked about.👍 |
As mentioned during the meeting, the test suite for the The test fixtures are stored as TS in order to make it easier to generate some of them programmatically and to define a few of the custom formatters, but it'd be pretty straightforward to transform them to a different format. The tests are published under the MIT license, and are therefore pretty free to use. As the sources for these tests are in MF1, they'll need to be transformed to an MF2 data model either live or as a pre-stage in order to test layers built on top of that. |
Referencig #165 (comment) , cause is a great start to design and plan how test suite should work and is already functional. My ideia here is to isolate the data source and have a group of generic test value(inputs/expected results), to be reused across different implementations of the MF (something like this independent of the final format) or we can start as we here and choose the format later |
Nominating this as a blocker, as the test suite is explicitly listed as one of our deliverables. |
We should have a group of standard sentences that could be used as a test cases for all possible implementations of message format. They must cover all possible casuistics
We have an example here for selectors.
The text was updated successfully, but these errors were encountered: