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
Automatic testing of latexify is currently a little painful since it relies on precise equality between the string generated by a function call and a string typed out in the test script. Generating such tests is pretty easy using the Latexify.@generate_test macro, but this exact string matching gives no leeway for making otherwise inconsequential changes to how latexify formats its output.
Is there a way of testing that latexify gives the desired result without being completely inflexible when it comes to making small changes?
This is related to the question of what should be considered part of the API, #77.
The text was updated successfully, but these errors were encountered:
Automatic testing of latexify is currently a little painful since it relies on precise equality between the string generated by a function call and a string typed out in the test script. Generating such tests is pretty easy using the
Latexify.@generate_test
macro, but this exact string matching gives no leeway for making otherwise inconsequential changes to howlatexify
formats its output.Is there a way of testing that
latexify
gives the desired result without being completely inflexible when it comes to making small changes?This is related to the question of what should be considered part of the API, #77.
The text was updated successfully, but these errors were encountered: