view doc/RUNNING_TESTS @ 1080:5bd8c86cfa6a issue_540

Makes the Publication model act as an activity; overloading the default ActivitiesController#index view in the Bibliography Plugin in order to differentiate Publications from the other event types.

* Known issues:
** route to /activities is not working (only to /activity);
** publication cache needs to be implemented in the model, not in the helper;
** when a publication is added to n projects, n events are created (all with the same content).

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.
You can run `ruby test/unit/issue_test.rb` for an each test.

Before running tests, 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.