RE: [PEAR-QA] Unit tests requiring a database or other system specific infos
| From: | Lukas Smith | Date: | Wed, 03 Sep 2003 06:39:07 +0000 |
| Subject: | RE: [PEAR-QA] Unit tests requiring a database or other system specific infos | ||
| References: | 1 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-177@lists.php.net to get a copy of this message | ||
> From: Daniel Khan [mailto:dk@webcluster.at]
> Sent: Wednesday, September 03, 2003 8:05 AM
> Lukas Smith wrote:
>
> > > The main question is if this is an overkill. Is automatic testing
> > really
> > > needed? ATM the unit tests are mainly a way for me to don't break
> > > exiting features while extending the package.
> >
> > Yes automatic testing is really needed. It makes a huge differences.
> > Especially in terms of BC. Little things might slip through. However
a
> > well written unit test suite will prevent this sort of thing.
>
> Does this now mean that we should try to provide shellscripts to do an
> interaktive
> 'make test'.
> On the other hand some people update PEAR using cronjobs.
>
> One possible way would be to provide a way to configure PEAR itself
for
> testing.
> I am thinking of a config file where the DSN to a test db and maybe
other
> settings
> are tested. Only if this is available each 'pear install foo' ends up
in a
> automatic test if
> provided by the package.
Ok, here you are touching on long term projects, which should be
addressed as soon as possible. At some point it would be cool if
packages get automatic unit testing when uploaded. And also automatic
testing is done when they are installed.
So if you want to start working on this all the better!
Regards,
Lukas