Rather than doing manual book keeping to plan the number of tests to run in each TAP suite, conclude each run with done_testing() summing up the the number of tests that ran. This removes the need for maintaning and updating the plan count at the expense of an accurate count of remaining during the test suite runtime. This patch has been discussed a number of times, often in the context of other patches which updates tests, so a larger number of discussions can be found in the archives. Reviewed-by: Julien Rouhaud <rjuju123@gmail.com> Reviewed-by: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org> Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> Reviewed-by: Michael Paquier <michael@paquier.xyz> Reviewed-by: Kyotaro Horiguchi <horikyota.ntt@gmail.com> Discussion: https://postgr.es/m/DD399313-3D56-4666-8079-88949DAC870F@yesql.se |
||
---|---|---|
.. | ||
t | ||
.gitignore | ||
Makefile | ||
README |
README
src/test/authentication/README Regression tests for authentication =================================== This directory contains a test suite for authentication. SSL certificate authentication tests are kept separate, in src/test/ssl/, because they are more complicated, and are not safe to run in a multi-user system. Running the tests ================= NOTE: You must have given the --enable-tap-tests argument to configure. Run make check or make installcheck You can use "make installcheck" if you previously did "make install". In that case, the code in the installation tree is tested. With "make check", a temporary installation tree is built from the current sources and then tested. Either way, this test initializes, starts, and stops a test Postgres cluster. See src/test/perl/README for more info about running these tests.