Mercurial > hg > soundsoftware-site
view doc/RUNNING_TESTS @ 586:658cfb481618 feature_36
Order BibTeX entry types in a sensible order for presentation to user, instead of alphabetically by BibTeX name as previously (requires database re-seed).
Provide a label for each entry type, and use it in the edit dropdown and show page.
Omit duplicate entry type (conference) from edit dropdown.
Use existing entry attribute labels in show_bibtex_fields.
author | Chris Cannam <chris.cannam@soundsoftware.ac.uk> |
---|---|
date | Fri, 12 Aug 2011 13:15:05 +0100 |
parents | 513646585e45 |
children | cbb26bc654de |
line wrap: on
line source
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 =================== Redmine 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 ============================= Redmine supports using LDAP for user authentications. To test LDAP with Redmine, 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 127.0.0.1 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.