Re: List TAP test files in makefiles

Hi,

On 2025-08-23 12:11:51 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > FWIW, I find the autoconf/make test run experience completely unusable. It
> > literally is made me embark on getting away from it. I don't understand how
> > people stand it.
>
> Interesting perspective, because from where I sit the testing aspect
> is the weakest part of our meson setup: it seems to be very much
> all-or-nothing, whereas the makefiles allow you to run any particular
> test suite you want.

Meson definitely allows to run just some of the test. You can list all tests
with
meson test --list

And you can run testsuites (like all the recovery tests) with
  meson test --suite recovery
or individual tests with
  meson test test_misc/003_check_guc


> Maybe this is just a lack of documentation?

Yea. Partially because that's generic information about meson (i.e. not
postgres specific stuff) and partially because there were some doc patches
that we ended up not finding agreement upon approach-wise.


> I find the lack of any equivalent to installcheck to be
> particularly distressing, since it means you can't repeat
> a test without paying for "make temp-install" every time.

If you just want to skip the install (reusing the prior install), you can do
that with
 meson test --no-suite setup

That's basically the equivalent of NO_TEMP_INSTALL (which isn't documented
either :( )


> Admittedly that doesn't work for a test that needs particular
> non-default installation settings, but that's a minority
> of our tests.

You can run all tests against a running postgres by doing
  meson test --setup running


Unless somebody else volunteers (please!), I guess I should write up a
patch...

Greetings,

Andres Freund