Tests are not indicative?

[ps-george]

In #175, it passes CI but we aren't sure if it works live.

We should be able to gain a certain amount of confidence that a commit works from whether CI passes or not.

• Check CI is working
• Parser tail rec #175
• Long file (tail-recursive parser) test #180
• Move CI to Zestylogic/fmark
• Review the reasons for the 4 ignored tests
• Maybe reintroduce parallelism in testing (recall disabling it because it broke our tests for some reason, probably a bug in a library that is fixed now?)

[ymherklotz]

CI is working: https://travis-ci.org/ymherklotz/FMark

We just need to add a test that parses a 10000 line markdown file for example, hopefully under 1sec.

[ps-george]

Do we test the bundled .js output?

[ps-george]

Does CI still work after switching repo? Is it still at /ymherklotz/FMark? @ymherklotz any plan to move it to zestylogic/FMark or is it all good to leave it where it is?

[ymherklotz]

Just moved it to https://travis-ci.org/Zestylogic/FMark. Going to fix it in the documentation.

[ps-george]

What was the reason that we ignored these 4 tests? Time?

Maybe they will be okay to include after #175 is merged and #179 is done?

[ymherklotz]

One of them is one of mine, which is a broken property test, don't know about the others.