Penrose tests (unit, assertion, property-based) about penrose HOT 7 CLOSED

@wodeni I've set up the testing infrastructure. See the main comment in this issue for more information. You're welcome to start writing tests for the parsers! I haven't written any for the Substance, Style, or Server modules yet, and indeed adding tests for them would be a very useful form of documentation.

from penrose.

@wodeni Also, regarding the revised parser, two of the examples here seem to be failing due to parser issues.

from penrose.

@wodeni Do you know if I can get the label sizes (and any other object info sent by snap) without running the server? As of now, in mainRetFinal, since the optimization doesn't interact with snap, the label sizes are zero, which makes the regression tests inconsistent with what shows up in the browser.

from penrose.

The label size is dependent on the font and font size used in client.js. Remember initially we assumed the letters to be monospaced but right now they are not due to the current font (palatino). Any chance to let the server run at least once?

from penrose.

I would be fine with running the server during the tests. Can we write a version of the server that terminates and returns a result (or several results, if we want to run multiple tests)?

from penrose.

I was trying to get Travis CI working with our repo and found that the tests now do not compile. The reason might be the changes in Substance module (?). In any case, there are some tests to could add to the test suite:

• DSLL parsing
• Substance Core language
• Substance type checking
• (future) Style type checking

from penrose.

Closing now that we have a working test suite in TS.

from penrose.