| @@ -1,35 +1,36 | |||
|
|
1 | 1 | Installing gems for testing |
|
|
2 | 2 | =========================== |
|
|
3 | 3 | |
|
|
4 | 4 | Run `rake gems RAILS_ENV=test` to list the required gems. Run |
|
|
5 | 5 | `rake gems:install RAILS_ENV=test` to install any missing gems. |
|
|
6 | 6 | |
|
|
7 | 7 | Running Tests |
|
|
8 | 8 | ============= |
|
|
9 | 9 | |
|
|
10 | 10 | Run `rake --tasks test` to see available tests. |
|
|
11 | 11 | `rake test` will run the entire testsuite. |
|
|
12 | You can run `ruby test/unit/issue_test.rb` for an each test. | |
|
|
12 | 13 | |
|
|
13 |
Before running |
|
|
|
14 | Before running tests, you need to configure both development | |
|
|
14 | 15 | and test databases. |
|
|
15 | 16 | |
|
|
16 | 17 | Creating test repositories |
|
|
17 | 18 | =================== |
|
|
18 | 19 | |
|
|
19 | 20 | Redmine supports a wide array of different version control systems. |
|
|
20 | 21 | To test the support, a test repository needs to be created for each of those. |
|
|
21 | 22 | |
|
|
22 | 23 | Run `rake --tasks test:scm:setup` for a list of available test-repositories or |
|
|
23 | 24 | run `rake test:scm:setup:all` to set up all of them |
|
|
24 | 25 | |
|
|
25 | 26 | Creating a test ldap database |
|
|
26 | 27 | ============================= |
|
|
27 | 28 | |
|
|
28 | 29 | Redmine supports using LDAP for user authentications. To test LDAP |
|
|
29 | 30 | with Redmine, load the LDAP export from test/fixtures/ldap/test-ldap.ldif |
|
|
30 | 31 | into a testing LDAP server. Test that the ldap server can be accessed |
|
|
31 | 32 | at 127.0.0.1 on port 389. |
|
|
32 | 33 | |
|
|
33 | 34 | Setting up the test ldap server is beyond the scope of this documentation. |
|
|
34 | 35 | The OpenLDAP project provides a simple LDAP implementation that should work |
|
|
35 | 36 | good as a test server. |
General Comments 0
You need to be logged in to leave comments.
Login now