Chris@909: Installing gems for testing
Chris@909: ===========================
Chris@909: 
Chris@909: Run `rake gems RAILS_ENV=test` to list the required gems.  Run 
Chris@909: `rake gems:install RAILS_ENV=test` to install any missing gems.
Chris@909: 
Chris@909: Running Tests
Chris@909: =============
Chris@909: 
Chris@909: Run `rake --tasks test` to see available tests.
Chris@909: `rake test` will run the entire testsuite.
Chris@909: You can run `ruby test/unit/issue_test.rb` for an each test.
Chris@909: 
Chris@909: Before running tests, you need to configure both development
Chris@909: and test databases.
Chris@909: 
Chris@909: Creating test repositories
Chris@909: ===================
Chris@909: 
Chris@909: Redmine supports a wide array of different version control systems.
Chris@909: To test the support, a test repository needs to be created for each of those.
Chris@909: 
Chris@909: Run `rake --tasks test:scm:setup` for a list of available test-repositories or
Chris@909: run `rake test:scm:setup:all` to set up all of them
Chris@909: 
Chris@909: Creating a test ldap database
Chris@909: =============================
Chris@909: 
Chris@909: Redmine supports using LDAP for user authentications.  To test LDAP
Chris@909: with Redmine, load the LDAP export from test/fixtures/ldap/test-ldap.ldif
Chris@909: into a testing LDAP server.  Test that the ldap server can be accessed
Chris@909: at 127.0.0.1 on port 389.
Chris@909: 
Chris@909: Setting up the test ldap server is beyond the scope of this documentation.
Chris@909: The OpenLDAP project provides a simple LDAP implementation that should work
Chris@909: good as a test server.