jro_apps/redmine Commit - r9642:12ea96066bb4

2

===========================

2

===========================

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.

5

the test dependencies. Then, run `bundle install`.

6

Then, run `bundle install`.

7

6

8

Running Tests

7

Running Tests

9

=============

8

=============

10

9

11

Run `rake --tasks test` to see available tests.

10

Run `rake --tasks test` to see available tests.

12

`rake test` ~~will~~ run the entire test~~suite.~~

11

Run `rake test` to run the entire test suite (note that this will drop

13

You can run `ruby test/unit/issue_test.rb` for an each test.

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

Before running tests, you need to configure both development

16

Before running tests, you need to configure both development

16

and test databases.

17

and test databases.

17

18

Creating test repositories

19

Creating test repositories

19

===================

20

==========================

20

21

Redmine supports a wide array of different version control systems.

22

Redmine supports a wide array of different version control systems.

22

To test the support, a test repository needs to be created for each of those.

23

To test the support, a test repository needs to be created for each of those.

23

24

Run `rake --tasks test:scm:setup` for a list of available test-repositories or

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

Creating a test ldap database

32

Creating a test ldap database

28

=============================

33

=============================

29

34

30

Redmine supports using LDAP for user authentications. To test LDAP

35

Redmine supports using LDAP for user authentications. To test LDAP

31

with Redmine, load the LDAP export from test/fixtures/ldap/test-ldap.ldif

36

with Redmine, load the LDAP export from test/fixtures/ldap/test-ldap.ldif

32

into a testing LDAP server. ~~Test that the ldap~~ server can be accessed

37

into a testing LDAP server. Make sure that the LDAP server can be accessed

33

at 127.0.0.1 on port 389.

38

at 127.0.0.1 on port 389.

34

39

35

Setting up the test ~~ldap~~ server is beyond the scope of this documentation.

40

Setting up the test LDAP server is beyond the scope of this documentation.

36

The OpenLDAP project provides a simple LDAP implementation that should work

41

The OpenLDAP project provides a simple LDAP implementation that should work

37

good as a test server.

42

good as a test server.

43

44

If the LDAP is not available, the tests that need it will be skipped.

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

             ===========================
             Remove your .bundle/config if you've already installed Redmine without
-            the test dependencies.
+            the test dependencies. Then, run `bundle install`.
-            Then, run `bundle install`.
             Running Tests
             =============
             Run `rake --tasks test` to see available tests.
-            `rake test` will run the entire testsuite.
+            Run `rake test` to run the entire test suite (note that this will drop
-            You can run `ruby test/unit/issue_test.rb` for an each test.
+            and recreate your test database)
+            You can run `ruby test/unit/issue_test.rb` for running a single test case.
             Before running tests, you need to configure both development
             and test databases.
             Creating test repositories
-            ===================
+            ==========================
             Redmine supports a wide array of different version control systems.
             To test the support, a test repository needs to be created for each of those.
             Run `rake --tasks test:scm:setup` for a list of available test-repositories or
-            run `rake test:scm:setup:all` to set up all of them
+            run `rake test:scm:setup:all` to set up all of them. The repositories are
+            unpacked into {redmine_root}/tmp/test.
+            If the test repositories are not present, the tests that need them will be
+            skipped.
             Creating a test ldap database
             =============================
             Redmine supports using LDAP for user authentications.  To test LDAP
             with Redmine, load the LDAP export from test/fixtures/ldap/test-ldap.ldif
-            into a testing LDAP server.  Test that the ldap server can be accessed
+            into a testing LDAP server. Make sure that the LDAP server can be accessed
             at 127.0.0.1 on port 389.
-            Setting up the test ldap server is beyond the scope of this documentation.
+            Setting up the test LDAP server is beyond the scope of this documentation.
             The OpenLDAP project provides a simple LDAP implementation that should work
             good as a test server.
+            If the LDAP is not available, the tests that need it will be skipped.