On Thu, 6 Sep 2007, Andreas Volz wrote:
> Am Wed, 5 Sep 2007 23:07:34 -0500 schrieb andres: > >> I'm writting some Edje development documentation and realizing how >> many code examples all around the docs are broken over small details. >> Which is ok by me but it could be very discouraging to others. >> >> I think we should commit all code examples to a separate folder and >> setup the nightly build system to compile them (or run some test >> script for the interpreted languages). > > There're a lot of tests in the examples dir of eflpp. Would be nice to > compile (and run) all tests in a nightly test and see the results at > the next day. This would save me some time while developing eflpp. I > think other libs may benefit also. > > So this is a good idea. Perhaps it's also a good idea to start writing > more classic unit tests and run them each night. i want to write some, using the check library, gcov and lcov. I currently have some problems using lcov when the source code is not is the same directory tree than the tests (raster wants them in the test/ dir). I'll try again this week end Vincent ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
