##// END OF EJS Templates
jro_apps » redmine
RSS
Updates the doc about the configurable test LDAP host....
Jean-Philippe Lang -
r14709:9110b543b518
parent child
Show More
Side by Side Unified
Context file:
r14709:9110b543b518 Loading diff...:
Show file before | Show file after | Hide comments
@@ -1,70 +1,73
1 Installing gems for testing
1 Installing gems for testing
2 ===========================
2 ===========================
3
3
4 Remove your .bundle/config if you've already installed Redmine without
4 Remove your .bundle/config if you've already installed Redmine without
5 the test dependencies. Then, run `bundle install`.
5 the test dependencies. Then, run `bundle install`.
6
6
7 Running Tests
7 Running Tests
8 =============
8 =============
9
9
10 Run `rake --tasks test` to see available tests.
10 Run `rake --tasks test` to see available tests.
11 Run `rake test` to run the entire test suite (except the tests for the
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).
12 Apache perl module Redmine.pm and Capybara tests, see below).
13
13
14 You can run `ruby test/unit/issue_test.rb` for running a single test case and
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.
15 `ruby test/unit/issue_test.rb -n test_create` for running a single test.
16
16
17 Before running tests, you need to configure both development
17 Before running tests, you need to configure both development
18 and test databases.
18 and test databases.
19
19
20 Creating test repositories
20 Creating test repositories
21 ==========================
21 ==========================
22
22
23 Redmine supports a wide array of different version control systems.
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.
24 To test the support, a test repository needs to be created for each of those.
25
25
26 Run `rake --tasks test:scm:setup` for a list of available test-repositories or
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
27 run `rake test:scm:setup:all` to set up all of them. The repositories are
28 unpacked into {redmine_root}/tmp/test.
28 unpacked into {redmine_root}/tmp/test.
29
29
30 If the test repositories are not present, the tests that need them will be
30 If the test repositories are not present, the tests that need them will be
31 skipped.
31 skipped.
32
32
33 Creating a test ldap database
33 Creating a test LDAP database
34 =============================
34 =============================
35
35
36 Redmine supports using LDAP for user authentications. To test LDAP
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
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
38 into a testing LDAP server. Make sure that the LDAP server can be accessed
39 at 127.0.0.1 on port 389.
39 at 127.0.0.1 on port 389.
40
40
41 If your LDAP server is not running on localhost, you can use the
42 REDMINE_TEST_LDAP_SERVER environment variable to specify another host.
43
41 Setting up the test LDAP server is beyond the scope of this documentation.
44 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
45 The OpenLDAP project provides a simple LDAP implementation that should work
43 good as a test server.
46 good as a test server.
44
47
45 If the LDAP is not available, the tests that need it will be skipped.
48 If the LDAP is not available, the tests that need it will be skipped.
46
49
47 Running Redmine.pm tests
50 Running Redmine.pm tests
48 ========================
51 ========================
49
52
50 (work in progress)
53 (work in progress)
51
54
52 Running the tests for the Redmine.pm perl module needs a bit more setup.
55 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.
56 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
57 See: http://www.redmine.org/projects/redmine/wiki/Repositories_access_control_with_apache_mod_dav_svn_and_mod_perl
55
58
56 You need an empty repository accessible at http://127.0.0.1/svn/ecookbook
59 You need an empty repository accessible at http://127.0.0.1/svn/ecookbook
57 Then, you can run the tests with:
60 Then, you can run the tests with:
58 `ruby test\extra\redmine_pm\repository_subversion_test.rb`
61 `ruby test\extra\redmine_pm\repository_subversion_test.rb`
59
62
60 If you svn server is not running on localhost, you can use the REDMINE_TEST_DAV_SERVER
63 If your svn server is not running on localhost, you can use the
61 environment variable to specify another host.
64 REDMINE_TEST_DAV_SERVER environment variable to specify another host.
62
65
63 Running Capybara tests
66 Running Capybara tests
64 ======================
67 ======================
65
68
66 You need to have PhantomJS WebDriver listening on port 4444:
69 You need to have PhantomJS WebDriver listening on port 4444:
67 `phantomjs --webdriver 4444`
70 `phantomjs --webdriver 4444`
68
71
69 Capybara tests can be run with:
72 Capybara tests can be run with:
70 `rake test:ui`
73 `rake test:ui`
General Comments 0
You need to be logged in to leave comments. Login now