Re: tests in test directory

2007-10-19 Thread Massimo Manghi
It also may help to keep the development of the apache-1 and
apache-2 together, at least to fix their behavior in
well defined common tests as long as we imagine the 2
modules as providing the same functionalities in 2
different webservers. After all is this what we want?
Having just apache-2 to take care of would give much more 
freedom to the development and simplify the tests.

David, you're the policy maker here, what do you think?
Maybe 1_0 is stable enough to be the final release for
apache1.x?

 -- Massimo


On Fri, 19 Oct 2007 19:22:07 +0300, Valery Masiutsin wrote
 Hello,  guys !
 
 During the next week i'll try to concentrate my attention on tcl/rvt
 test scripts
 that could be found in tests directory.
 First of all it needs to be tuned for apache 2 support, after that
 i'll need to  revue the scripts, probably  add a number of new ones.
 The purpose of this is to create some sort of automated suite which
 will allow us to test different aspects of rivet2 module. And will
 clear show up what does not work, and will make easy to catch up
 regressions.
 All thoughts on this topic are welcome.
 
 Regards Valery
 


--
Universita' degli Studi di Parma (http://www.unipr.it)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Request for trunk clean up

2007-10-19 Thread David Welton
 Files that needs to be deleted:
 configure
 Makefile.in
 src/apache-1/Makefile.in
 src/apache-1/Makefile.in
 src/Makefile.in
 doc/Makefile.in
 config.h.in

 Correct me if i am missing something.

Done.

-- 
David N. Welton
http://www.welton.it/davidw/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tests in test directory

2007-10-19 Thread David Welton
 During the next week i'll try to concentrate my attention on tcl/rvt
 test scripts
 that could be found in tests directory.
 First of all it needs to be tuned for apache 2 support, after that
 i'll need to  revue the scripts, probably  add a number of new ones.
 The purpose of this is to create some sort of automated suite which
 will allow us to test different aspects of rivet2 module. And will
 clear show up what does not work, and will make easy to catch up
 regressions.
 All thoughts on this topic are welcome.

My thoughts are basically thankyou!.  Automated testing is a great
way of keeping a project free of bugs - every time you find a new one,
you can add a test that demonstrates it, and makes sure the bug won't
come back at some later date when someone says this code is weird,
let's try getting rid of it and see what happens.

-- 
David N. Welton
http://www.welton.it/davidw/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]