ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.


TODO: documentation on how to test ChiliProject.

From doc/RUNNING_TESTS.rdoc

= Installing gems for testing

Run `rake gems RAILS_ENV=test` to list the required gems.  Run 
`rake gems:install RAILS_ENV=test` to install any missing gems.

== Running Tests

Run `rake --tasks test` to see available tests.
`rake test` will run the entire testsuite.

Before running `rake test` you need to configure both development
and test databases.

== Creating test repositories

ChiliProject supports a wide array of different version control systems.
To test the support, a test repository needs to be created for each of those.

Run `rake --tasks test:scm:setup` for a list of available test-repositories or
run `rake test:scm:setup:all` to set up all of them

== Creating a test ldap database

ChiliProject supports using LDAP for user authentications.  To test LDAP
with ChiliProject, load the LDAP export from test/fixtures/ldap/test-ldap.ldif
into a testing LDAP server.  Test that the ldap server can be accessed
at on port 389.

Setting up the test ldap server is beyond the scope of this documentation.
The OpenLDAP project provides a simple LDAP implementation that should work
good as a test server.