postgresql

History

Tom Lane c992dca26e Clarify the README files for the various separate TAP-based test suites. Explain the difference between "make check" and "make installcheck". Mention the need for --enable-tap-tests (only some of these did so before). Standardize their wording about how to run the tests.		2018-06-19 19:30:50 -04:00
..
t	Don't fall off the end of perl functions	2018-05-27 09:08:42 -04:00
.gitignore	Add .gitignore for src/test/authentication/tmp_check.	2017-03-20 18:27:36 +01:00
Makefile	Add installcheck support to more test suites	2018-01-23 07:11:38 -05:00
README	Clarify the README files for the various separate TAP-based test suites.	2018-06-19 19:30:50 -04:00

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.