gitlabhq/spec/requests
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
..
admin Add optional signup. 2013-01-18 11:57:31 +01:00
api API: tests to show incorrect behavior when reaching project limit 2013-02-14 11:13:25 +01:00
atom Fixed dashboard show specs 2013-01-27 13:20:23 +02:00
security Fix security spec 2013-01-05 00:49:43 +02:00
gitlab_flavored_markdown_spec.rb should be green build now :) 2013-01-15 19:18:52 +02:00
issues_spec.rb Continue refactoring. Use repostory and team 2013-01-04 08:43:25 +02:00
notes_on_merge_requests_spec.rb fix notes specs 2013-01-31 13:13:17 +02:00
notes_on_wall_spec.rb fix notes specs 2013-01-31 13:13:17 +02:00
profile_spec.rb Test the delete acount option. 2013-02-11 13:06:37 +01:00
projects_deploy_keys_spec.rb Rspec fixes 2013-01-04 18:50:31 +02:00
projects_spec.rb A bit of spinach tests 2013-01-09 08:14:05 +03:00
search_spec.rb Rspec fixes 2013-01-04 18:50:31 +02:00
snippets_spec.rb Rspec fixes 2013-01-04 18:50:31 +02:00