-
Notifications
You must be signed in to change notification settings - Fork 5
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
Test suite #10
Comments
Yeah definitely; there's already this document that starts to test converting Google Doc-specific markup into text (like native links, making sure headers come through as plain text, bullets come back as We could do something similar in order to test all of the different components of the spec. We could also explore making a more formal test suite out of a series of text files and the objects they should be converted into. Splitting them out into multiple tests would make it easier to maintain, and possibly easier to track down bugs in individual parsers. But that makes the scaffolding around the test more complex. Or maybe we could split the difference, and automatically combine the list of txt/json pairs into one big google document + what the output should look like, to let you do an all-or-nothing spot check as well? What would be the most useful? |
A single test document would be most useful in my case, but it may make On Mon, Mar 30, 2015 at 11:43 AM Michael Strickland <
|
Hey @noamross, Over the weekend I ported the specs from archieml-js over to a folder in this repo as individual ArchieML files with the json-encoded output they're supposed to translate into. https://github.com/newsdev/archieml.org/tree/gh-pages/test/1.0 For example, this test describes the test with
The first file in that directory,
The idea is that you could use either the individual tests, or the The Google docs-specific tests are a little outside the scope for the moment, since the spec doesn't take an opinion on what HTML markup should be generated by Google Doc formatting. But maybe a second, simpler document that just tests formatting (and not parser logic) could be used for that? |
Would you be able to publicly share a google doc (or several) that can act as a common test suite for everything in ArchieML? This will be especially useful as the spec is updated. It should be publicly accessible for viewing and copying but not editing.
The text was updated successfully, but these errors were encountered: