This is a stronger proposal IMHO. We have loads of easy-to-test stuff in support/ and to a lesser degree crypt/ where a breakage could break the whole node.
Higher level unit tests would also be pretty interesting. Once you've added the infrastructure for some high-level tests, we could add new ones relatively easily, and it also lets us do real-code simulations with multiple nodes in a single VM and irrelevant layers disabled. On Tue, Mar 20, 2007 at 03:44:43PM +0100, Sback wrote: > Hi, > > this is the second proposal. As before comments will be appreciated! > > Thanks in advance ;) > > Sback > > ************************************************************************** > Alberto Bacchelli > sbackG at Gmail.com > > Project Title: > Freenet Test Suite creation and current unit tests improvement > > Abstract: > Currently there are only few tests in the repository (less than 15 classes, > about 1 test method per class and often used without JUnit support). > It is a big problem when introducing new features into the project. > The main goal of this project is to create an appropriate test > suite for the project. > Of course it is not possible -in three months- to cover all the project > with tests, for this reason it is necessary to find the most runned code > (maybe with the help of a profiler) and concentrate on that. > With a software to quantify the tests code coverage then it will be > possible to verify > when a sufficient percentual will be reached. > > Benefits to the Freenet Community: > This project will enormously help further developing of > the Freenet project giving a really better assurance that new features > won't beake the current implementation. > > Deliverables: > * Create specific method tests with a fine granularity on most used code > * Create tests with a bigger granularity to verify and quanitfy nodes > quality > setting up multiple nodes in the same VM with different options. > > Project Schedule: > - Analysis of most used code througth profilers[e.g. 0,1] and developers > point of view: 2/3 weeks (12/14 days) > - Most used code test covering[e.g. 2,3]: 3/4 weeks (18/20 days) > - Higher level tests: 3/4 weeks (18/20 days) > > Brief Biography: > I am a 24 years-old Italian student, currently doing my second MS year > at the Universite` Libre de Bruxelles. > I graduated "cum laude" in March 2006 with a thesis on the development > of a Java based software for > managing congressual events througth RFID cards. > > I am also a system administrator in a little company in Italy and for > two years I have been administrator for my university in a nonuniform > cluster managing 2000 users and offering internal and external services. > I have studied for six months with Professor Roel Wuyts[4] on tests > based software engineering. > > I am supporter of Agile software development and I am very focused on > software engineering based on eXtreme Programming, which I think is the best > development form for open source software: regular contributions on which > you can run tests and get community feedbacks. > > I support free software also because I like working with different > people and listen different opinions to get the best from our > heterogeneity to create something evolved.. When I get in touch with > something new that I cannot understand fully, I usually prefer to get > involved with it and explore it to find my own critic. > > > [0] http://ejp.sourceforge.net/ > [1] http://jcoverage.sourceforge.net/ > [2] http://csdl.ics.hawaii.edu/Tools/JBlanket/ > [3] http://hansel.sourceforge.net/ > [4] http://decomp.ulb.ac.be/roelwuyts/ > **********************************************************************8 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20070320/2960504c/attachment.pgp>
