[Pkg-shadow-devel] Re: [Pkg-shadow-commits] r407 - in branches/experimental/debian: . patches

[Tomasz Kłoczko]

On Tue, 26 Jul 2005, Nicolas [iso-8859-1] François wrote:
[..]
> I'm not sure an automated test suite will be feasible. Also, it will have
> to be secure (i.e. I don't want to test the no password for root
> functionality on one of my online boxes) (something running on a
> dedicated chroot?).

I think about script for run tests after full install (runed not on build 
stage). It will allow cut amout of time for testing.
By lack of this testing (as element of release procedure) I'm release
4.0.11 with trival bug :>

> Does anybody have an idea how we can automate an "su" with a password, and
> then check the environment variables set in the shell?

Probably using expect or dejagnu can help on this.

> I'm not sure it will be easy to have the same test suite (e.g. for Debian,
> we will test with a Debian PAM, and we may want to test how adduser behave
> with a new useradd), but we can certainly share a lot.
> 
> A first step could be a simple paper with check box (and maybe scripts to
> help checking the result).
> This could be added to a TODO: writing clear use cases with
> pre-conditions, steps and expected behaviors.
> 
> If we manage to get something working, we should inform Marc Haber (Debian
> adduser maintainer). He sent a mail on debian-devel and asked for help
> (and mentioned he would be interested by somebody setting up a test
> suite)

I thing only about anything what can minimize release buggy code.
If it will require some special enviroment for testing (?) ... never mind.
If it will require manual runing (?) .. never mind.

kloczek
-- 
-----------------------------------------------------------
*Ludzie nie mają problemów, tylko sobie sami je stwarzają*
-----------------------------------------------------------
Tomasz KÅ‚oczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek at rudy.mif.pg.gda.pl*