On Thursday 28 February 2008 21:14, Alberto Bacchelli wrote: > Matthew Toseland wrote: > > On Thursday 28 February 2008 19:50, Alberto Bacchelli wrote: > > > >> Matthew Toseland wrote: > >> > >>> How exactly does this work? I presume it assumes that the current code is > >>> correct, and generates a suite of tests to verify that it stays that way? > >>> > >>> > >> Yes, you are right. This is the target of regression tests. > >> There are a few tools that could perform this task (generating > >> regression tests from current code), > >> but I found that JUnit Factory produces the best results > >> > > > > Sounds like a good idea. Obviously handwritten unit tests are also a good > > idea, but if nobody wants to write them then generated regression tests will > > do. Auto-generated regression tests should be clearly marked as such. > > > They require a particular library and by default they are in a different > dir (called agitar-test) > than usual tests. So they are easily discernible. > > I could start generating them if you agree. Should I use the trunk or > another branch to show you how they work? > I am sure they won't create problems, so imho we could use the trunk > directly.
Trunk is fine, since they won't be part of a running node. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20080228/d3bd941f/attachment.pgp>
