gitlabhq/spec
Sebastian Ziebell 1a01fc0c96 API: tests to show incorrect behavior when reaching project limit
When reaching the project limit the API returns an error code 404 on the last possible
project. The project itself is created and is available in the database (seems valid).
A similar behavior can be observed when reaching the project limit via web client, but
in this case the user is notified that the maximum number of projects is reached. The project
itself is still created and can be accessed.

Tests are added to check the behavior when reaching the project limit or one tries
to exceed it via the API.
2013-02-14 11:13:25 +01:00
..
contexts Improve CreateContext call. Fixed test 2013-01-18 20:21:13 +02:00
controllers remove unused autogenerated files 2013-01-24 22:31:48 +02:00
factories add path and path_with_namespace to api project entity 2013-01-31 09:11:35 +02:00
helpers remove unused autogenerated files 2013-01-24 22:31:48 +02:00
lib fixing tests after refactoring 2013-02-11 20:28:27 +02:00
mailers Fix mailer tests 2013-02-01 15:37:21 +02:00
models Constants in Events looks good now 2013-02-13 15:48:16 +04:00
observers Constants in Events looks good now 2013-02-13 15:48:16 +04:00
requests API: tests to show incorrect behavior when reaching project limit 2013-02-14 11:13:25 +01:00
routing Test to show incorrect routing to Compare controller 2013-02-12 19:28:37 +11:00
support Fixed: post-receive, project remove, tests 2013-02-05 12:47:50 +02:00
tasks/gitlab Fix routing issues when navigating over tree, commits etc 2012-12-25 06:14:05 +03:00
workers fixing tests after refactoring 2013-02-11 20:28:27 +02:00
factories.rb Constants in Events looks good now 2013-02-13 15:48:16 +04:00
factories_spec.rb Factories spec refactoring after #1616 2012-10-03 13:33:31 +03:00
seed_project.tar.gz Rspec test repo replaced.\nMerge Requests improved 2012-03-13 23:54:49 +02:00
spec_helper.rb No gitolite in project any more 2013-02-11 19:16:59 +02:00