regression tests for pkg-jed packages

Jörg Sommer joerg at alea.gnuu.de
Tue May 29 16:45:32 UTC 2007


Hallo Rafael,

Rafael Laboissiere schrieb am Tue 29. May, 17:19 (+0200):
> * Jörg Sommer <joerg at alea.gnuu.de> [2007-05-28 23:37]:
> > I would change the check_installation into check_package and do this there.
> 
> The advantage of adding regression tests is that is helps *_a lot_* to
> detect problem in all architectures.  Thanks to regression tests, I already
> detected problems in 64-bits architectures that do not manifest themselves
> when I build packages on i386.  Regression tests tremendously adds value to
> the package and I think we should include them.

Of what checks do you think? I see the problem that you can't do so much
checks, because the package isn't installed. You can't check if the
buildin paths are correct and if all files are installed—a reason why I
wouldn't use lib/ in jed as JED_LIB, because this give a wrong view.

What about forcing this for all packages? I suggest we add two targets
check-arch and check-indep they run some tests after build, e.g. the last
command of binary-arch must be -$(MAKE) debian/check-arch and for
binary-indep respectively.

We should do as much tests as possible. I know this is very vague, but it
shows the direction.

What do you think about rebuild as much as possible from scratch? I found
out how John builds the configure script. Should we remove it and rebuild
it?

Schöne Grüße, Jörg.
-- 
[dpkg] We are the apt. Resistance is futile. You will be packaged.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 481 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-jed-devel/attachments/20070529/fd622a73/attachment.pgp 


More information about the Pkg-jed-devel mailing list