summaryrefslogtreecommitdiffabout
path: root/README
authorSergey Poznyakoff <gray@gnu.org.ua>2014-11-13 06:51:35 (GMT)
committer Sergey Poznyakoff <gray@gnu.org.ua>2014-11-13 06:51:35 (GMT)
commitc761f530a0d6bd8fddfff6568dad6dc79161eefe (patch) (side-by-side diff)
treec0bd823f7db8ed66ee705f3fb890f53941959771 /README
parentc7956b1f1f22937970f29b1f0d4a8a7a7957274d (diff)
downloadvmod-dbrw-c761f530a0d6bd8fddfff6568dad6dc79161eefe.tar.gz
vmod-dbrw-c761f530a0d6bd8fddfff6568dad6dc79161eefe.tar.bz2
Version 2.0release-2.0
Diffstat (limited to 'README') (more/less context) (ignore whitespace changes)
-rw-r--r--README19
1 files changed, 10 insertions, 9 deletions
diff --git a/README b/README
index 5ee4f46..93f6f7e 100644
--- a/README
+++ b/README
@@ -137,13 +137,14 @@ This will build the module. Finally, do the following command as root:
* Testing
Testing the module requires access to an SQL database which will be
-populated with the test data. Before running the test suite, you
-have to create the database, or the user (role), which is able to
-create it. For example, for MySQL:
+populated with the test data. You can either create that database
+yourself, or let the testsuite create it. The easiest way is to
+create a user (role), which is able to create the database. For
+example, in MySQL:
GRANT ALL PRIVILEGES on dbrw_test.* to dbrw_test@localhost;
-Or, for PostgreSQL:
+Or, in PostgreSQL:
CREATE ROLE dbrw_test WITH LOGIN CREATEDB
@@ -188,7 +189,7 @@ Database user.
Password to connect to the server (if necessary).
-Ideally, the tests should succeed. If they don't, that don't
+Ideally, the tests should succeed. If they don't, that does not
necessarily indicates a problem in the module:
The tests will be skipped if the supplied credentials are insufficient
@@ -206,12 +207,12 @@ create or populate the test database. In this case, act as described
above.
Finally, if some or all of the tests were marked as failed, that
-indicates a bug in the module itself, or in the test suite. In this
-case, the file testsuite.log will contain detailed logs. Additional
+indicates a bug either in the module itself, or in the test suite. In
+this case, the file testsuite.log will contain detailed logs. Additional
information can then be found in the directory testsuite.dir. Please
send these data to the developer.
-Notice that the testsuite tries to create the database only once.
+Notice, that the testsuite tries to create the database only once.
Subsequent invocations of `make check' will use the existing database.
Similarly, if it failed to create the database, the failure will be
memorized and all subsequent runs will just skip all checks. To clear
@@ -220,7 +221,7 @@ the state, run `make clean' in the directory tests, e.g.:
make -C tests clean
make check
-You can also supply the database credentials in invocation of
+You can also supply the database credentials to invocation of
configure:
./configure --with-varnish-source=/usr/src/varnish-3.0.1\

Return to:

Send suggestions and report system problems to the System administrator.