[devtools] make PostgresTestDataBaseHandler start its own postgresql
Don't depend on postgresql already running on the system, or on a static
config.
To use this, set the configcls attribute of your CubicWebTC-derived test
class to PostgresApptestConfiguration.
Caveats:
- this won't work with several tests running concurrently from the
same directory, since each would start its own cluster with a shared
data directory and stomp on each other's toes
- you need initdb/pg_ctl in $PATH, e.g /usr/lib/postgresql/$version/bin
on Debian/Ubuntu systems.
Closes #3489631
<html>
<head>
<!-- dependencies -->
<script type="text/javascript" src="../../data/jquery.js"></script>
<script src="../../data/cubicweb.python.js" type="text/javascript"></script>
<script src="../../data/cubicweb.js" type="text/javascript"></script>
<script src="../../data/cubicweb.compat.js" type="text/javascript"></script>
<script src="../../data/cubicweb.htmlhelpers.js" type="text/javascript"></script>
<!-- qunit files -->
<script type="text/javascript" src="../../../devtools/data/qunit.js"></script>
<link rel="stylesheet" type="text/css" media="all" href="../../../devtools/data/qunit.css" />
<!-- test suite -->
<script src="cwmock.js" type="text/javascript"></script>
<script src="test_htmlhelpers.js" type="text/javascript"></script>
</head>
<body>
<div id="main"> </div>
<h1 id="qunit-header">cubicweb.htmlhelpers.js functions tests</h1>
<h2 id="qunit-banner"></h2>
<ol id="qunit-tests">
</body>
</html>