On Wed, May 7, 2008 at 6:29 AM, Vincent Torri <[EMAIL PROTECTED]> wrote: > raster, dan and me had a small discussion about the location of unit > tests. Dan and me were for putting them in efl_lib/tests and raster in > e17/tests/efl_lib > > raster arguments are for putting them outside efl_lib/ are > > 1) lots of data in src/. Indeed, maybe big files can be needed. That can > increase the size of the tarball. > 2) end users and packagers do not need them > 3) if unit tests are in the tarball, packager can maybe think that they > must ship them. > > raster: if you think that i have forgotten something, please add any > argument
I just want to raise some point regarding putting unit test inside the released tarball. It should ease the work of a release manager, just run make dist-check and if all the tests passed, you are ready for a release. Another situation where it can help, is when someone compile the library from source and has some problem, so we could just ask him to run make check and send us the report. This should help developper that use our lib by providing an easier learning path. In any case, having unit test and coverage report will be really helpfull, so as soon as everyone agreed on Vincent proposal, I am for adding the necessary stuff to eet at least (but all efl libs should have their own unit test, I think). -- Cedric BAIL ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
