[ckan-changes] commit/ckan: dread: [doc]: Adding instructions about test dependencies added.

[Bitbucket]

1 new changeset in ckan:

http://bitbucket.org/okfn/ckan/changeset/a2c6711ef9fd/
changeset:   a2c6711ef9fd
branches:    
user:        dread
date:        2011-05-27 12:22:46
summary:     [doc]: Adding instructions about test dependencies added.
affected #:  1 file (172 bytes)

--- a/README.txt	Thu May 26 21:38:13 2011 +0100
+++ b/README.txt	Fri May 27 11:22:46 2011 +0100
@@ -282,6 +282,10 @@
 
     pip install --ignore-installed nose
 
+Install the dependencies for tests::
+
+    pip install --ignore-installed -r pyenv/src/ckan/pip-requirements-test.txt
+
 At this point you will need to deactivate and then re-activate your
 virtual environment to ensure that all the scripts point to the correct
 locations:
@@ -312,7 +316,7 @@
 Test configurations
 -------------------
 
-The default way to run tests is defined in test.ini (which is the default config file for nose - change it with option "--with-pylons"). This specifies to use Sqlite and sets faster_db_test_hacks, which are compromises.
+The default way to run tests is defined in test.ini (which is the default config file for nose - change it with option "--with-pylons"). This specifies to use Sqlite and takes short cuts when clearing out the database between tests, which are compromises.
 
 ::
 
@@ -333,7 +337,7 @@
 
      nosetests ckan/tests --ckan --with-pylons=test-core.ini
  
-The test suite takes a long time to run against standard PostgreSQL (approx. 15 minutes, or close to an hour on Ubuntu/10.04 Lucid).
+The test suite takes a long time to run against standard PostgreSQL (approx. 15 minutes, or close to an hour on some machines (maybe a 64 bit issue?).
 
 This can be improved to between 5 and 15 minutes by running PostgreSQL in memory and turning off durability, as described at <http://www.postgresql.org/docs/9.0/static/non-durability.html>.

Repository URL: https://bitbucket.org/okfn/ckan/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.