This repo offers general help with installing extensions and lessons we've learned
One of the original goals was to write a test suite to confirm that newly installed extensions were not breaking the ckan instance. What we did was to get the built-in test suite running see http://docs.ckan.org/en/ckan-2.6.0/contributing/test.html This probably does NOT satisfy that requirement - since extensions are modular running the ckan test suite only tests the core code. Having said that, you can run the tests by doing
run-tests-easy output-file.txt
They currently take about 25 minutes to run and use nohup so you can log out.
In spite of not living up to the requirement, a few useful things have come out of this:
- a possible problem with our set up (see ckan/ckan#3465)
- if we do modify the ckan core, we have a functioning test suite
- MOST IMPORTANTLY, we have a test-core.ini file and database tables which enable us to run an extension's own tests.
- Loads of ckan knowledge gained!
Here's what's in this repo:
- ckan-testing-setup.txt how we set up our ckan instance to run the ckan test suite
- install-extension.txt general outline of how to install extensions and test ckan
- ckan-tests-bin scripts for testing and utility scripts
- versions.txt versions and locations of ckan and extensions configured in /etc/ckan/default/production.ini
- extensions-installed.txt what we've installed and notes on how we did it