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

From: Ryo Kanbayashi <kanbayashi(dot)dev(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(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-03-01 10:45:15
Message-ID: CANOn0EyrD=kgrZZnr-xEr5K=KxZ3j0MjxWG4bMcdNZSzWby-mQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 28, 2025 at 11:27 PM Fujii Masao
<masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
> 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!

Thanks for review:)

>
> + '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?

I replaced "notice" to "err_warn_msg"

> 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...

I couldn't too. So places are not changed.

> +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.

I reflected above.

---
Great regards,
Ryo Kanbayashi

Attachment Content-Type Size
ecpg-notice-regress-patch-tap-ver-rebased.patch application/octet-stream 5.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2025-03-01 11:30:47 Re: [PATCH] Add get_bytes() and set_bytes() functions
Previous Message Yuya Watari 2025-03-01 10:06:38 Re: [PoC] Reducing planning time when tables have many partitions