Mercurial > hg > soundsoftware-site
comparison .svn/pristine/15/1563561117c58a8d11c2e6605c5ed92c8394ca39.svn-base @ 1464:261b3d9a4903 redmine-2.4
Update to Redmine 2.4 branch rev 12663
author | Chris Cannam |
---|---|
date | Tue, 14 Jan 2014 14:37:42 +0000 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
1296:038ba2d95de8 | 1464:261b3d9a4903 |
---|---|
1 Installing gems for testing | |
2 =========================== | |
3 | |
4 Remove your .bundle/config if you've already installed Redmine without | |
5 the test dependencies. Then, run `bundle install`. | |
6 | |
7 Running Tests | |
8 ============= | |
9 | |
10 Run `rake --tasks test` to see available tests. | |
11 Run `rake test` to run the entire test suite (except the tests for the | |
12 Apache perl module Redmine.pm and Capybara tests, see below). | |
13 | |
14 You can run `ruby test/unit/issue_test.rb` for running a single test case and | |
15 `ruby test/unit/issue_test.rb -n test_create` for running a single test. | |
16 | |
17 Before running tests, you need to configure both development | |
18 and test databases. | |
19 | |
20 Creating test repositories | |
21 ========================== | |
22 | |
23 Redmine supports a wide array of different version control systems. | |
24 To test the support, a test repository needs to be created for each of those. | |
25 | |
26 Run `rake --tasks test:scm:setup` for a list of available test-repositories or | |
27 run `rake test:scm:setup:all` to set up all of them. The repositories are | |
28 unpacked into {redmine_root}/tmp/test. | |
29 | |
30 If the test repositories are not present, the tests that need them will be | |
31 skipped. | |
32 | |
33 Creating a test ldap database | |
34 ============================= | |
35 | |
36 Redmine supports using LDAP for user authentications. To test LDAP | |
37 with Redmine, load the LDAP export from test/fixtures/ldap/test-ldap.ldif | |
38 into a testing LDAP server. Make sure that the LDAP server can be accessed | |
39 at 127.0.0.1 on port 389. | |
40 | |
41 Setting up the test LDAP server is beyond the scope of this documentation. | |
42 The OpenLDAP project provides a simple LDAP implementation that should work | |
43 good as a test server. | |
44 | |
45 If the LDAP is not available, the tests that need it will be skipped. | |
46 | |
47 Running Redmine.pm tests | |
48 ======================== | |
49 | |
50 (work in progress) | |
51 | |
52 Running the tests for the Redmine.pm perl module needs a bit more setup. | |
53 You need an Apache server with mod_perl, mod_dav_svn and Redmine.pm configured. | |
54 See: http://www.redmine.org/projects/redmine/wiki/Repositories_access_control_with_apache_mod_dav_svn_and_mod_perl | |
55 | |
56 You need an empty repository accessible at http://127.0.0.1/svn/ecookbook | |
57 Then, you can run the tests with: | |
58 `ruby test\extra\redmine_pm\repository_subversion_test.rb` | |
59 | |
60 If you svn server is not running on localhost, you can use the REDMINE_TEST_DAV_SERVER | |
61 environment variable to specify another host. | |
62 | |
63 Running Capybara tests | |
64 ====================== | |
65 | |
66 You need to have PhantomJS WebDriver listening on port 4444: | |
67 `phantomjs --webdriver 4444` | |
68 | |
69 Capybara tests can be run with: | |
70 `rake test:ui` |