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