Re: Testing

Okay. The tests. Is it so, that if I make a new feature, I also make a
test for it? What if that new feature runs without errors, but is very
slow, uses plenty of memory etc. ? Can it leak memory? Is there a test
for all new features? What happens, if there is no test for a feature?
Is there a link from a bug to change tests?

Well, when I look at the release history, and for example 7.3, there was
7.3.4 that came out before 7.4. So there are not very many releases.
That means, that there can't be very many serious bugs left around. Many
bugs would mean that there would need to be minor releases quite often.

Usually it is not just luck, that a product works. But I would like to
tell, that there is a reason, and that also the future releases are very
reliable ;-) Certainly, I would not like to tell, that as a user, you
are the tester... But of course, it is different, if we say, that as a
user, you have the ability to test the software, and verify that it
works properly ;-)

Jussi

Shridhar Daithankar wrote:

> Jussi Mikkola wrote:
>
>> I noticed, that there is not any story of how PostgreSQL is tested. I
>> could find a FAQ, and some stuff about regression tests, but what I
>> am looking for, is that is there a small group, that is responsible
>> for testing, what tools they are using, if bugs are found, what
>> happens then etc.
>
>
> When you compile postgresql from sources, after make is done, you can
> run make check which runs lots of tests to make sure that it works
> according to design.
>
> After that, you can use it for development and production. If you find
> a bug, submit a bug report to pgsql-bugs(at)postgresql(dot)org(dot)
>
> There is no special testing team. The user base is the testing team..:-)
>
> HTH
>
> Shridhar
>
>

--
Jussi Mikkola Partner, Project Manager
Bonware Oy gsm +358 40 830 7561
Tekniikantie 21 tel +358 9 2517 5570
02150 Espoo fax +358 9 2517 5571
Finland www.bonware.com