@Janiczek made a good point in #119
"Do you know of some diverse test suites publicly available on GitHub? It would be good to test the new code on something nontrivial."
Can we add another Travis job that runs some real-world tests? i.e. running the elm-test suites for some stable Elm projects? Preferably the tests in this repo would be blocking, while tests from other repos are informational.
@drathier since Travis jobs are repo-based, I think the way to do this "informationally" would be to create a separate repo which ran the real-world tests.
@Janiczek made a good point in #119 "Do you know of some diverse test suites publicly available on GitHub? It would be good to test the new code on something nontrivial."
Can we add another Travis job that runs some real-world tests? i.e. running the elm-test suites for some stable Elm projects? Preferably the tests in this repo would be blocking, while tests from other repos are informational.