Feedback-ID: ie0a040ee:Fastmail
Message-ID: <daa90384-0085-4ac7-bbec-bcde1fc3ec1d@eisentraut.org>
Date: Thu, 13 Jun 2024 16:01:23 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Contributing test cases to improve coverage
To: J F <jonathanfoo0523@gmail.com>, pgsql-hackers@lists.postgresql.org
References: <CAEFLKGhVEP4_N4T4KQ75av7CEJreJpY1j2T+Dxq96dyJ1khBhg@mail.gmail.com>
Content-Language: en-US
From: Peter Eisentraut <peter@eisentraut.org>
In-Reply-To: <CAEFLKGhVEP4_N4T4KQ75av7CEJreJpY1j2T+Dxq96dyJ1khBhg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/daa90384-0085-4ac7-bbec-bcde1fc3ec1d%40eisentraut.org>
Precedence: bulk

On 12.06.24 18:44, J F wrote:
> (a) The regression test suite is run by a parallel scheduler, with some 
> test cases dependent on previous test cases. If I just add my test case 
> as part of the parallel scheduler’s tests, it might not work, since 
> previous test cases in the scheduler might already create the same 
> table, for instance.

Yes, you need to take care of that somehow.  Some test files put all 
their test objects in a schema.  Others are careful to drop all test 
objects at the end.  Or you just have to pick non-conflicting names.

> (b) How do I get my test cases reviewed and ultimately included in a 
> future release of PostgreSQL?

Perhaps start with

https://wiki.postgresql.org/wiki/Development_information

and in particular

https://wiki.postgresql.org/wiki/Submitting_a_Patch