On Thu, 6 Sep 2007 23:26:58 +0200 (CEST) Vincent Torri
<[EMAIL PROTECTED]> wrote:

> 
> 
> 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).

The nightly build system tries to be generic.  So to support testing,
we would need to define some standard way of invoking those tests.  On
the other hand, the nature of E development means that most tests
proggies are GUI apps that are not as easily tested.

Most E stuff is written in C using autotools, so that will be where
testing infrastructure should be developed first.

I think the simplest way would be similar to how the gendoc script is
currently supported.  If a gendoc script is found in the packages base
directory, it is used to generate docs.  So a test.sh script could be
used in a similar way.

The other thing to keep in mind is that the system currently runs on
the E web server.  We don't want to soak up resources running tests.
Everything is run with the lowest CPU and IO priority, so performance
testing is probably a waste of time.

Attachment: signature.asc
Description: PGP signature

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to