| @@ -1,37 +1,44 | |||
|
|
1 | 1 | Installing gems for testing |
|
|
2 | 2 | =========================== |
|
|
3 | 3 | |
|
|
4 | 4 | Remove your .bundle/config if you've already installed Redmine without |
|
|
5 | the test dependencies. | |
|
|
6 | Then, run `bundle install`. | |
|
|
5 | the test dependencies. Then, run `bundle install`. | |
|
|
7 | 6 | |
|
|
8 | 7 | Running Tests |
|
|
9 | 8 | ============= |
|
|
10 | 9 | |
|
|
11 | 10 | Run `rake --tasks test` to see available tests. |
|
|
12 |
`rake test` |
|
|
|
13 | You can run `ruby test/unit/issue_test.rb` for an each test. | |
|
|
11 | Run `rake test` to run the entire test suite (note that this will drop | |
|
|
12 | and recreate your test database) | |
|
|
13 | ||
|
|
14 | You can run `ruby test/unit/issue_test.rb` for running a single test case. | |
|
|
14 | 15 | |
|
|
15 | 16 | Before running tests, you need to configure both development |
|
|
16 | 17 | and test databases. |
|
|
17 | 18 | |
|
|
18 | 19 | Creating test repositories |
|
|
19 | =================== | |
|
|
20 | ========================== | |
|
|
20 | 21 | |
|
|
21 | 22 | Redmine supports a wide array of different version control systems. |
|
|
22 | 23 | To test the support, a test repository needs to be created for each of those. |
|
|
23 | 24 | |
|
|
24 | 25 | Run `rake --tasks test:scm:setup` for a list of available test-repositories or |
|
|
25 | run `rake test:scm:setup:all` to set up all of them | |
|
|
26 | run `rake test:scm:setup:all` to set up all of them. The repositories are | |
|
|
27 | unpacked into {redmine_root}/tmp/test. | |
|
|
28 | ||
|
|
29 | If the test repositories are not present, the tests that need them will be | |
|
|
30 | skipped. | |
|
|
26 | 31 | |
|
|
27 | 32 | Creating a test ldap database |
|
|
28 | 33 | ============================= |
|
|
29 | 34 | |
|
|
30 | 35 | Redmine supports using LDAP for user authentications. To test LDAP |
|
|
31 | 36 | with Redmine, load the LDAP export from test/fixtures/ldap/test-ldap.ldif |
|
|
32 |
into a testing LDAP server. |
|
|
|
37 | into a testing LDAP server. Make sure that the LDAP server can be accessed | |
|
|
33 | 38 | at 127.0.0.1 on port 389. |
|
|
34 | 39 | |
|
|
35 |
Setting up the test |
|
|
|
40 | Setting up the test LDAP server is beyond the scope of this documentation. | |
|
|
36 | 41 | The OpenLDAP project provides a simple LDAP implementation that should work |
|
|
37 | 42 | good as a test server. |
|
|
43 | ||
|
|
44 | If the LDAP is not available, the tests that need it will be skipped. | |
General Comments 0
You need to be logged in to leave comments.
Login now