| @@ -1,22 +1,24 | |||
|
|
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 | 12 | |
|
|
13 | Before running `rake test` you need to configure both development | |
|
|
14 | and test databases. | |
|
|
13 | 15 | |
|
|
14 | 16 | Creating test repositories |
|
|
15 | 17 | =================== |
|
|
16 | 18 | |
|
|
17 | 19 | Redmine supports a wide array of different version control systems. |
|
|
18 | 20 | To test the support, a test repository needs to be created for each of those. |
|
|
19 | 21 | |
|
|
20 | 22 | Run `rake --tasks test:scm:setup` for a list of available test-repositories or |
|
|
21 | 23 | run `rake test:scm:setup:all` to set up all of them |
|
|
22 | 24 | |
General Comments 0
You need to be logged in to leave comments.
Login now