aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorSergey Poznyakoff <gray@gnu.org.ua>2014-11-13 08:51:35 +0200
committerSergey Poznyakoff <gray@gnu.org.ua>2014-11-13 08:51:35 +0200
commitc761f530a0d6bd8fddfff6568dad6dc79161eefe (patch)
treec0bd823f7db8ed66ee705f3fb890f53941959771 /README
parentc7956b1f1f22937970f29b1f0d4a8a7a7957274d (diff)
downloadvmod-dbrw-c761f530a0d6bd8fddfff6568dad6dc79161eefe.tar.gz
vmod-dbrw-c761f530a0d6bd8fddfff6568dad6dc79161eefe.tar.bz2
Version 2.0release-2.0
Diffstat (limited to 'README')
-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:
137* Testing 137* Testing
138 138
139Testing the module requires access to an SQL database which will be 139Testing the module requires access to an SQL database which will be
140populated with the test data. Before running the test suite, you 140populated with the test data. You can either create that database
141have to create the database, or the user (role), which is able to 141yourself, or let the testsuite create it. The easiest way is to
142create it. For example, for MySQL: 142create a user (role), which is able to create the database. For
143example, in MySQL:
143 144
144 GRANT ALL PRIVILEGES on dbrw_test.* to dbrw_test@localhost; 145 GRANT ALL PRIVILEGES on dbrw_test.* to dbrw_test@localhost;
145 146
146Or, for PostgreSQL: 147Or, in PostgreSQL:
147 148
148 CREATE ROLE dbrw_test WITH LOGIN CREATEDB 149 CREATE ROLE dbrw_test WITH LOGIN CREATEDB
149 150
@@ -188,7 +189,7 @@ Database user.
188 189
189Password to connect to the server (if necessary). 190Password to connect to the server (if necessary).
190 191
191Ideally, the tests should succeed. If they don't, that don't 192Ideally, the tests should succeed. If they don't, that does not
192necessarily indicates a problem in the module: 193necessarily indicates a problem in the module:
193 194
194The tests will be skipped if the supplied credentials are insufficient 195The 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
206above. 207above.
207 208
208Finally, if some or all of the tests were marked as failed, that 209Finally, if some or all of the tests were marked as failed, that
209indicates a bug in the module itself, or in the test suite. In this 210indicates a bug either in the module itself, or in the test suite. In
210case, the file testsuite.log will contain detailed logs. Additional 211this case, the file testsuite.log will contain detailed logs. Additional
211information can then be found in the directory testsuite.dir. Please 212information can then be found in the directory testsuite.dir. Please
212send these data to the developer. 213send these data to the developer.
213 214
214Notice that the testsuite tries to create the database only once. 215Notice, that the testsuite tries to create the database only once.
215Subsequent invocations of `make check' will use the existing database. 216Subsequent invocations of `make check' will use the existing database.
216Similarly, if it failed to create the database, the failure will be 217Similarly, if it failed to create the database, the failure will be
217memorized and all subsequent runs will just skip all checks. To clear 218memorized 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.:
220 make -C tests clean 221 make -C tests clean
221 make check 222 make check
222 223
223You can also supply the database credentials in invocation of 224You can also supply the database credentials to invocation of
224configure: 225configure:
225 226
226 ./configure --with-varnish-source=/usr/src/varnish-3.0.1\ 227 ./configure --with-varnish-source=/usr/src/varnish-3.0.1\

Return to:

Send suggestions and report system problems to the System administrator.