Doc cleanup.
git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@9825 e93f8b46-1217-0410-a6f0-8f06a7374b81
This commit is contained in:
parent
13dced9d76
commit
12ea96066b
|
@ -2,36 +2,43 @@ Installing gems for testing
|
||||||
===========================
|
===========================
|
||||||
|
|
||||||
Remove your .bundle/config if you've already installed Redmine without
|
Remove your .bundle/config if you've already installed Redmine without
|
||||||
the test dependencies.
|
the test dependencies. Then, run `bundle install`.
|
||||||
Then, run `bundle install`.
|
|
||||||
|
|
||||||
Running Tests
|
Running Tests
|
||||||
=============
|
=============
|
||||||
|
|
||||||
Run `rake --tasks test` to see available tests.
|
Run `rake --tasks test` to see available tests.
|
||||||
`rake test` will run the entire testsuite.
|
Run `rake test` to run the entire test suite (note that this will drop
|
||||||
You can run `ruby test/unit/issue_test.rb` for an each test.
|
and recreate your test database)
|
||||||
|
|
||||||
|
You can run `ruby test/unit/issue_test.rb` for running a single test case.
|
||||||
|
|
||||||
Before running tests, you need to configure both development
|
Before running tests, you need to configure both development
|
||||||
and test databases.
|
and test databases.
|
||||||
|
|
||||||
Creating test repositories
|
Creating test repositories
|
||||||
===================
|
==========================
|
||||||
|
|
||||||
Redmine supports a wide array of different version control systems.
|
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.
|
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 --tasks test:scm:setup` for a list of available test-repositories or
|
||||||
run `rake test:scm:setup:all` to set up all of them
|
run `rake test:scm:setup:all` to set up all of them. The repositories are
|
||||||
|
unpacked into {redmine_root}/tmp/test.
|
||||||
|
|
||||||
|
If the test repositories are not present, the tests that need them will be
|
||||||
|
skipped.
|
||||||
|
|
||||||
Creating a test ldap database
|
Creating a test ldap database
|
||||||
=============================
|
=============================
|
||||||
|
|
||||||
Redmine supports using LDAP for user authentications. To test LDAP
|
Redmine supports using LDAP for user authentications. To test LDAP
|
||||||
with Redmine, load the LDAP export from test/fixtures/ldap/test-ldap.ldif
|
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
|
into a testing LDAP server. Make sure that the LDAP server can be accessed
|
||||||
at 127.0.0.1 on port 389.
|
at 127.0.0.1 on port 389.
|
||||||
|
|
||||||
Setting up the test ldap server is beyond the scope of this documentation.
|
Setting up the test LDAP server is beyond the scope of this documentation.
|
||||||
The OpenLDAP project provides a simple LDAP implementation that should work
|
The OpenLDAP project provides a simple LDAP implementation that should work
|
||||||
good as a test server.
|
good as a test server.
|
||||||
|
|
||||||
|
If the LDAP is not available, the tests that need it will be skipped.
|
||||||
|
|
Loading…
Reference in New Issue