macros: define %postgresql_tests_run

* lib/rpm/macros.d/macros.in (postgresql_tests_run): New macro for
the cases when the temporary testing postgresql cluster doesn't
need any specific configuration.

Author: praiskup

NEWS

@@ -6,6 +6,10 @@ New in 7.0 version:
 
 * Simplified build against SCLs with --with-scl option.
 
+* New test macro %postgresql_tests_run.
+
+Incompatible changes in 7.0 version
+
 * The %pgtest_init && %pgtest_start renamed to %postgresql_tests_init and
   %postgresql_tests_start.
 

lib/rpm/macros.d/macros.in

@@ -8,17 +8,18 @@
 
 %@NAME_SERVICE_VARNAME@_module_requires Requires: @NAME_SERVICE_VARNAME@-server(:MODULE_COMPAT_@PGMAJORVERSION@)
 
-%_@NAME_SERVICE_VARNAME@_tests_lib "@PKG_TESTS_LIB@"
-
 # Initialize the PostgreSQL tests environment.  This is supposed to be invoked
 # in prep/build/install (where you plan to run the testsuite), while it defines
 # several useful shell variables and provies useful commands.  Effect of this
 # command end with shell exit.
-%@NAME_SERVICE_VARNAME@_tests_init %_@NAME_SERVICE_VARNAME@_tests_lib
+%@NAME_SERVICE_VARNAME@_tests_init . "@PKG_TESTS_LIB@"
 
 # Start the testing postgresql server, setting the actual unix user to be the
 # PostgreSQL admin.  The $PGHOST/$PGPORT are set appropriately, so psql is able
 # to run without passwords.  This also sets shell exit trap callback so that if
 # something goes wrong and package build fails, the temporary database is
 # automatically cleaned up.
 %@NAME_SERVICE_VARNAME@_tests_start pgtests_start
+
+# Initialize database and run server in one step, if this works well-enough.
+%@NAME_SERVICE_VARNAME@_tests_run %@NAME_SERVICE_VARNAME@_tests_init ; %@NAME_SERVICE_VARNAME@_tests_start