Re: [PATCH] Add regression tests of ecpg command notice (error / warning)

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Ryo Kanbayashi <kanbayashi(dot)dev(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Add regression tests of ecpg command notice (error / warning)
Date: 2025-02-28 14:27:09
Message-ID: 72206195-7000-4c81-a5d0-381a0d676cc4@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025/02/28 9:24, Ryo Kanbayashi wrote:
> I have rewrote my patch on TAP test sttyle :)
> File for build are also updated.

Thanks for updating the patch!

+ 'tests': [
+ 't/001_ecpg_notice.pl',
+ 't/002_ecpg_notice_informix.pl',

Since neither test emits "notice" messages, shouldn't the test file
names be revised to reflect this?

Also, I'm unsure if it's ideal to place input files directly under
the "t" directory. I looked for similar TAP tests with input files,
but I couldn't find any examples to guide this decision...

+program_help_ok('ecpg');
+program_version_ok('ecpg');
+program_options_handling_ok('ecpg');
+command_fails(['ecpg'], 'ecpg without arguments fails');

These checks seem unnecessary in 002 since they're already covered in 001.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message m.litsarev 2025-02-28 14:07:06 Re: SQL function which allows to distinguish a server being in point in time recovery mode and an ordinary replica