David Steele de816a0f57 Remove integration expect log testing. ... Integration expect log testing was originally used as a rough-and-ready way to make sure that certain code paths were being executed before the unit tests existed. Now that we have 100% unit test coverage (with expect log testing) the value of the integration expect tests seems minimal at best. But they do cause numerous issues: - Maintenance of the expect code and replacements that are required to keep logs reproducible. - Even a trivial change can cause massive churn in the expect logs, e.g. d9088b2. These changes should be minutely audited but since the expect logs have little value now it is seldom worth the effort. - The OS version used to do expect testing (RHEL7) can only be used to test one version of PostgreSQL. This makes it hard to balance the PostgreSQL version testing between OS versions. - When a commit affects expect logs it is not clear (especially for new developers) how to regenerate them and our contributing guide is silent on the issue. The goal is to migrate the integration tests to C and expect testing is not part of that plan. It seems best to get rid of them now.		2022-05-10 13:18:26 -04:00
..
MockAllTest.pm	Remove integration expect log testing.	2022-05-10 13:18:26 -04:00
MockArchiveStopTest.pm	Remove integration expect log testing.	2022-05-10 13:18:26 -04:00
MockArchiveTest.pm	Remove integration expect log testing.	2022-05-10 13:18:26 -04:00
MockExpireTest.pm	Remove integration expect log testing.	2022-05-10 13:18:26 -04:00
MockStanzaTest.pm	Remove integration expect log testing.	2022-05-10 13:18:26 -04:00