lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Gridly: simple Segmented Grid


From: Urs Liska
Subject: Re: Gridly: simple Segmented Grid
Date: Tue, 10 Feb 2015 22:20:43 +0100
User-agent: K-9 Mail for Android


Am 10. Februar 2015 20:35:23 MEZ, schrieb Matteo Ceccarello <address@hidden>:
>Dear Urs,
>
>Il 09/02/2015 10:16, Urs Liska ha scritto:
>> 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.
>I opened a pull request 
>(https://github.com/openlilylib/openlilylib/pull/60) which implements a
>
>very simple testing strategy. Library developers are able to configure 
>arbitrary lilypond files as test cases, so examples and other more 
>specific files can be used as test cases. So example files do not 
>necessarily need to be included in the tests.
>
>This still does not handle failure condition, for which I think we will
>
>need a full fledged testing framework. Anyway, the simple testing 
>strategy I'm proposing can already catch bugs like the one you pointed 
>out in this thread (btw, I fixed it, in the next days I'll merge the
>fix 
>into master).
>
>> 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.
>I have no experience in setting up Jenkins, I think that the tradeoffs 
>between running on Travis CI vs. a self-hosted Jenkins server need to
>be 
>evaluated, so further investigation is needed.

I've seen it, and as I've commented I won't be able to handle it in a timely 
manner. So any consideration by others is welcome.

Urs
>
>Bests,
>Matteo




reply via email to

[Prev in Thread] Current Thread [Next in Thread]