Re: Testing an extension exhaustively?

From: Steve Atkins <steve(at)blighty(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Testing an extension exhaustively?
Date: 2017-02-02 00:33:04
Message-ID: 1CF1F326-16FD-4A69-B653-E84097096893@blighty.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


> On Feb 1, 2017, at 4:03 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
>
> On 2/1/2017 3:39 PM, postgres user wrote:
>> If I have the Postgresql server installed on my machine i.e I have all the bins, libs and share directories of the Postgresql and I have the libs and sql's installed for one of the contrib extensions lets say "chkpass", how does one go about testing this extension exhaustively on the server? I ask this because I would want to do this manually first and then go about automating the testing of this extension. So rather than just execute CREATE EXTENSION and DROP EXTENSION I want some solid evidence that the extension is working fine under all circumstances and is not crashing the server at any moment? Looking for some new strategies and ideas to come my way through this.
>
> you would write test cases for all the functionality provided by this extension, same as you'd test any other sort of API.

And you might find http://pgtap.org convenient for doing that.

Cheers,
Steve

In response to

Browse pgsql-general by date

  From Date Subject
Next Message postgres user 2017-02-02 04:34:21 Using different GCC, CFLAGS, CCFLAGS and CPPFLAGS to compile Postgres and PostGIS?
Previous Message John R Pierce 2017-02-02 00:03:18 Re: Testing an extension exhaustively?