gitlabhq/spec/requests
Sebastian Ziebell 818caf0b5d API: refined status code handling when adding or updating a project member
When a user is added to a project that is already a member of, a status code 201 is now returned to
signal an idempotent operation. If something fails then instead of returning error code 404 different
more specific error codes are returned. Status code 400 (Bad request) is returned when a required
attribute, e.g. `access_level` is not given or 422 if there is a semantic error, e.g. should
the `access_level` have an unsupported value.

Specs are added to check these status codes.
2013-02-08 14:33:29 +01:00
..
admin Add optional signup. 2013-01-18 11:57:31 +01:00
api API: refined status code handling when adding or updating a project member 2013-02-08 14:33:29 +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
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