On 06/07/2012 11:36 AM, jvoisin wrote: > Since I want to do BDD (Behavior Driven Development) this summer, I am > wondering how > Debian-live (and, in a more global view, liveCD in general) is tested.
That is a particular interest of mine as well, and an idea I played with in this now defunct project: http://live.debian.net/gitweb?p=live-workbench.git;a=summary > It seems like the "mainstream way" for testing liveCD is autotest[2], but I > think it's a > little bit overkill for my purpose; this is why I am planing to use > lettuce[3]. Interesting. Due to my strong grounding in ruby, I had started this project using cucumber, the inspiration for lettuce. I had applied it only to the development of live-workbench itself (which, I must stress, is in no way functional at this time, nor is it likely to ever be, unless I have fresh inspiration to revive the project) and only had vague plans to later apply it to the results of live builds. As for whether Lettuce would be the best package to use, I don't know. I haven't thoroughly surveyed the available tools. Others to consider are: cucumber itself, cucumber-jvm and freshen. Of course, this is your project, so you choose the tool that suits you best. > Has anyone some clues or advices to share about this kind of problematic ? I'm not sure if I have much to offer, but I'd be happy to discuss the topic here and/or on irc (#debian-live @ irc.oftc.net, irc nick = SynrG). Ben -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
