Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Linux standards

I'm surprised at you. You know that we Unix developers never need to test 
our code :-).
Actually, for a target type of install, the test/validation should be 
performed as part of the install procedure. For an automated procedure 
under a package manager, test and validation could be done as separate and 
disjoint steps. Also, some applications don't lend themselves to scripted 
testing. An example would be a graphical email program. Once could add some 
non-graphical test hooks into the code. Validation could always be done. 
Prevalidation before the code is moved to the target, post validation after 
the move. And even a user level validation suite. 

On 20 Jun 2002 at 15:55, John Chambers wrote:

> Jerry Feldman writes:
> | Most of the better apps require the following steps:
> | 1. ./configure [ configure arguments ]
> | 2. make
> | 3. become root.
> | 4. make install
> | 5. become non-root.
> Hey, you forgot a very common (and important) step:
>   2.5. make test
> I'm always disappointed at packages that don't  have  this.
> Of  course,  writing  a  good test suite can take more work
> that writing the package itself ...
> _______________________________________________
> Discuss mailing list
> Discuss at

Jerry Feldman <gaf at>
Associate Director
Boston Linux and Unix user group PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /