Am 09.02.2015 um 09:56 schrieb Matteo Ceccarello:
Here I see room for starting some discussion on automated testing. I think that example files can serve also as test files, to check that code changes or version changes do not break things. Github has an associated continuous integration service called [Travis CI](https://travis-ci.org/) that runs test suites (or arbitrary commands) on each push. There is no explicit support for LilyPond, but I think that we can make it work anyway.
This is a good idea. But it would also imply that usage example files should be required to also cover failure conditions.
For openLilyLib I can also offer the openlilylib.org server for implementing continuous integration, but I would need help to set everything up (actually this is something I'd be quite interested in learning), for example with a Jenkins server.
Urs _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
