gitlabhq/spec/requests
Sebastian Ziebell fd01f3aacd API: fixes a few return codes for project snippets
When using project snippets via API the functions now provide status codes for
different situations other then only returning 404 error. If required parameters are missing,
e.g. `title` when creating a project snippet a 400 (Bad request) error is returned. The snippet
delete function now is idempotent and returns a 200 (Ok) regardless if the snippet with the
given id is available or not. Changing return codes of these functions has the advantage that
the 404 error is used only for resources, which are not available.

Tests added to check these status codes when handling project snippets.
2013-02-13 12:09:16 +01:00
..
admin Add optional signup. 2013-01-18 11:57:31 +01:00
api API: fixes a few return codes for project snippets 2013-02-13 12:09:16 +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