diff options
author | Sergey Poznyakoff <gray@gnu.org.ua> | 2014-11-13 08:51:35 +0200 |
---|---|---|
committer | Sergey Poznyakoff <gray@gnu.org.ua> | 2014-11-13 08:51:35 +0200 |
commit | c761f530a0d6bd8fddfff6568dad6dc79161eefe (patch) | |
tree | c0bd823f7db8ed66ee705f3fb890f53941959771 /README | |
parent | c7956b1f1f22937970f29b1f0d4a8a7a7957274d (diff) | |
download | vmod-dbrw-c761f530a0d6bd8fddfff6568dad6dc79161eefe.tar.gz vmod-dbrw-c761f530a0d6bd8fddfff6568dad6dc79161eefe.tar.bz2 |
Version 2.0release-2.0
Diffstat (limited to 'README')
-rw-r--r-- | README | 19 |
1 files changed, 10 insertions, 9 deletions
@@ -137,13 +137,14 @@ This will build the module. Finally, do the following command as root: | |||
137 | * Testing | 137 | * Testing |
138 | 138 | ||
139 | Testing the module requires access to an SQL database which will be | 139 | Testing the module requires access to an SQL database which will be |
140 | populated with the test data. Before running the test suite, you | 140 | populated with the test data. You can either create that database |
141 | have to create the database, or the user (role), which is able to | 141 | yourself, or let the testsuite create it. The easiest way is to |
142 | create it. For example, for MySQL: | 142 | create a user (role), which is able to create the database. For |
143 | example, 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 | ||
146 | Or, for PostgreSQL: | 147 | Or, 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 | ||
189 | Password to connect to the server (if necessary). | 190 | Password to connect to the server (if necessary). |
190 | 191 | ||
191 | Ideally, the tests should succeed. If they don't, that don't | 192 | Ideally, the tests should succeed. If they don't, that does not |
192 | necessarily indicates a problem in the module: | 193 | necessarily indicates a problem in the module: |
193 | 194 | ||
194 | The tests will be skipped if the supplied credentials are insufficient | 195 | 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 | |||
206 | above. | 207 | above. |
207 | 208 | ||
208 | Finally, if some or all of the tests were marked as failed, that | 209 | Finally, if some or all of the tests were marked as failed, that |
209 | indicates a bug in the module itself, or in the test suite. In this | 210 | indicates a bug either in the module itself, or in the test suite. In |
210 | case, the file testsuite.log will contain detailed logs. Additional | 211 | this case, the file testsuite.log will contain detailed logs. Additional |
211 | information can then be found in the directory testsuite.dir. Please | 212 | information can then be found in the directory testsuite.dir. Please |
212 | send these data to the developer. | 213 | send these data to the developer. |
213 | 214 | ||
214 | Notice that the testsuite tries to create the database only once. | 215 | Notice, that the testsuite tries to create the database only once. |
215 | Subsequent invocations of `make check' will use the existing database. | 216 | Subsequent invocations of `make check' will use the existing database. |
216 | Similarly, if it failed to create the database, the failure will be | 217 | Similarly, if it failed to create the database, the failure will be |
217 | memorized and all subsequent runs will just skip all checks. To clear | 218 | 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.: | |||
220 | make -C tests clean | 221 | make -C tests clean |
221 | make check | 222 | make check |
222 | 223 | ||
223 | You can also supply the database credentials in invocation of | 224 | You can also supply the database credentials to invocation of |
224 | configure: | 225 | configure: |
225 | 226 | ||
226 | ./configure --with-varnish-source=/usr/src/varnish-3.0.1\ | 227 | ./configure --with-varnish-source=/usr/src/varnish-3.0.1\ |