-
Notifications
You must be signed in to change notification settings - Fork 2
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
evaluate test cases #390
Comments
Coverage is lacking for:
|
Two conflicting thoughts:
|
Not using texml to generate our test files risks diverging unintentionally. However, this hasn't been a major problem in the past. I'm leaning more towards unit-testing because the tests would be easier to understand (and thus maintain). But that would move us even further from a texml-generated approach because texml is too slow to pre-process each snippet. I suppose we could keep the snippets for the unit tests separately but the XML would just be full of texml-generated boilerplate. What I'm hoping will happen: if we refactor to unit tests, we'll find which tests are too interconnected. That'll give us a few more complex test cases which we can then generate with texml. |
#447 makes me want to find time for this. |
Random note: perhaps texml's test files could serve as integration/snapshot tests. |
Anything we can do to improve things?
The text was updated successfully, but these errors were encountered: